In the morning i tried to bring back some stuff from UAT. When I tried to import my solution back to DEV I was getting errors. My solution contained Flows. Why do I use the classic admin interface to import solutions? Read this article: https://wordpress.com/block-editor/post/msolenacrm.blog/1608 I went the classic interface to import the solution. I've… Continue reading Import solution to CDS. Missing Connection references error…
Don't be like me! This is the JavaScript: var uriClientLegacy = "?$select = cca_legacyservicefee, defaultpricelevelid & $filter=accountid eq " + clientLookupId; Xrm.WebApi.retrieveMultipleRecords("account", uriClientLegacy).then( function success(result) { ... }, function (error) { console.log(error.message); // handle error conditions alert(error.message); }); And this is the execution result: {"error":{"code":"0x0","message":"The query parameter $select is not supported","innererror":{"message":"The query parameter $select is… Continue reading Xrm.WebApi. “The query parameter $select is not supported” error.
Well, as per the title. Watch your whitespace. For example, I was getting this error on the checker and tried to figure out what is wrong with the reference name. Flow Checker error When you use expressions you have to type things in. This is where you have to extra careful. Typing in expressions may… Continue reading Power Automate: watch your (white)space!
Life is pain... "The following filtering attributes are not valid:..." { "error": { "code": "0x80040203", "message": "The following filtering attributes are not valid: lastname" }} Fix the trigger ...error Remove the white space between the comma and the next attribute! A white space between filtering attributes causing the error. No white space between filtering attributes It is simple... always... after 🙂
Something Awesome About ... Power Platform and BizApps..Dev and Ops 