PL-400 · Question #367
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might h
The correct answer is B. No. The solution fails to meet the goal because throwing a custom exception in a synchronous plug-in will halt the transaction and display a generic error, not a custom message directly on the form for user resolution.
Question
Options
- AYes
- BNo
How the community answered
(19 responses)- A21% (4)
- B79% (15)
Why each option
The solution fails to meet the goal because throwing a custom exception in a synchronous plug-in will halt the transaction and display a generic error, not a custom message directly on the form for user resolution.
Throwing a custom exception does not display a user-friendly message on the form; it typically results in a transaction error dialog.
Throwing an InvalidPluginExecutionException in a synchronous plug-in will cause the current Dataverse operation to fail and display an error message to the user, but it will not display a custom message directly on the form fields or allow for immediate user resolution within the form context. For on-form validation messages, client-side scripting or specific Dataverse validation mechanisms integrated with the UI are required.
Concept tested: Synchronous plug-in error handling and user feedback
Source: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/write-plug-in
Community Discussion
No community discussion yet for this question.