One of the reasons why throwing the InvalidPluginExecutionException doesn’t show up error dialog could be that you would have Profiled that step with profile storage as Persist to Entity.
Stop Profiling and it should work as expected.
Check for more details on InvalidPluginExecutionException –
Hope it helps..
We might get this error while working with Web resource of type JavaScript.
Either it could be because the method doesn’t exist or it could be because of the incorrect syntax.
For a small file, it is easy to figure out, but for a large file, we could use online validator tools like
Fix the syntax error, upload and publish the file and the error should get fixed.
Hope it helps..
We might get the below error while using Xrm.WebAPI.
‘Bad Request – Error in query syntax.’
One of the reasons could be that while setting up the Lookup field, we haven’t removed the curly brackets.
Use the below function to replace/remove them.
Hope it helps..
We got the below error while trying to use the Relate function – “Value must be a data entity record”
As the error message clearly states and also if we see the syntax, the Relate function expects a record
Below was our formula for OnSelect, which was throwing the error
Here instead of passing the record, we were passing the table in the Relationship which was the reason for the error.
We changed it to store the ThisItem
And also updated the OnSelect
This fixed the issue for us.
Hope this helps..
Recently we created a custom page to be opened from the Ribbon / Command bar, however, the page was not opening for us, even though the function was running properly.
Here we had created the custom page from within the solution area, so we need to add this custom page to our model-driven app. (The other option is to create the page from the Modern App Designer.)
Open the app in the Modern App Designer and click on Add Page
Select Use an exiting custom page, select the page and uncheck the Show in navigation option as we are opening this page from the form.
Publish the app.
This time clicking on Open Custom page command/button on the form successfully opened the custom page for us.
Thanks to Andrew (https://butenko.pro/) for the solution.
Hope it helps..
Instead of hardcoding Combo box , we can bind it to the Choice / Option Set field of Dynamics 365 / Dataverse.
Format – Choices(DataSource[@columnname])
Check out the post that explains it – https://debajmecrm.com/how-to-bind-a-multiselect-choice-of-dataverse-to-a-combobox-in-canvas-apps/
Also check out – how to bind and do filter on multiselect combo box – https://youtu.be/5dSk5iOgT68?t=286
To learn about all the properties of Combo box refer – https://www.spguides.com/powerapps-combobox-control/
Hope it helps..
