Olena's Dynamics Blog (post-AI)
Writing as a human
Category: Business Applications
-
All the amazing docs, which help you to start are available here: https://docs.microsoft.com/en-us/powerapps/maker/portals/web-api-perform-operations#update-and-delete-entities-using-the-web-api https://docs.microsoft.com/en-us/powerapps/maker/portals/web-api-overview#web-api-operations I was testing the scenario where we had to workaround with the plugin: prior portal Web API times 🙂 it wasn’t possible to deactivate a record from a portal with a status different from the default one. Now it’s super easy!…
-
Recently, we run into the weird issue which we initially assessed as the upgrade to V9 related. The issue was that some form fields were aren’t marked as required based on the Account type based on the business logic. We use the unhealthy mix of scripts and business rules for the form logic. Also, we…
-
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…
-
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. When you use expressions you have to type things in. This is where you have to extra careful. It seams to look OK but in…
-
Something I won’t expect to discover. Yet, here I am! It’s all started with a very “simple” requirement to populate a read-only form field on change of another form field, Method. The fancy way it set up is when you select the field to change it pops up the window asking you if it was…
Olena's Dynamics Blog (post-AI) 