This post will explain how you can handle errors from a connector (or custom connector) and show a proper error message from the response of the API.
Whenever we use the Patch() function to create/update a row in Microsoft Dataverse, call an action of a (custom) connector or call a Power Automate cloud flow, there may be an error due to the server-side validation or an exception…
Continue Reading noreply@blogger.com (Linn Zaw Win)’s Article on their blog
Error Handling and Show Error Message from API in Canvas App
This post will explain how you can handle errors from a connector (or custom connector) and show a proper error message from the response of the API. Whenever we use the Patch() function to create/update a row in Microsoft Dataverse, call an action of a (custom) connector or call a Power Automate cloud flow, there may be an error due to the server-side validation or an exception being thrown by the underlying API.
Blog Syndicated with noreply@blogger.com (Linn Zaw Win)’s Permission
More About This Author
Array
Dyn365CE4 March 2024Open New Record Form with Pre-populated Fields Using Xrm.Navigation.navigateTo
Dyn365CE23 February 2024How to Fix Button in Modern Command Bar Disappearing After Grid Item Selection
Dyn365CE16 February 2024Keep Your Dataverse Solution Clean and Simple
Dyn365CE7 February 2024Refresh Main Form When New Child Row is Added in Subgrid via Quick Create Form in Model-Driven App
