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 –…
Continue Reading Nishant Rana’s Article on their blog
InvalidPluginExecutionException error dialog not showing up – Dynamis 365 / Dataverse
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 – https://learn.microsoft.com/en-us/power-apps/developer/data-platform/handle-exceptions#cancelling-the-current-operation https://learn.microsoft.com/en-us/power-apps/developer/data-platform/best-practices/business-logic/use-invalidpluginexecutionexception-plugin-workflow-activities Hope it helps..
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
- Dyn365CE7 May 2024Use Filter Array action to remove values from an array variable – Power Automate
- Dyn365CE6 May 2024Fixed – The latitude or longitude for the User record associated with this resource is invalid – Dynamics 365 Field Service /Dataverse
- Dyn365CE30 April 2024Use Geolocation Settings for Location Tracking and Auditing – Dynamics 365 Field Service
- Dyn365CE29 April 2024Fix the trigger – Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found operand types ‘Edm.Guid’ and ‘Edm.String’ for operator kind ‘Equal’ (Power Automate / Dataverse)