PL-400 practice question 22 of 35

A bank uses a Common Data Service solution to manage clients. Bank representatives perform client credit checks while the client is present. Credit…

Full set: 391 questions

Domain Extend the user experience

A bank uses a Common Data Service solution to manage clients. Bank representatives perform client credit checks while the client is present. Credit checks may take up to five minutes to complete. Bank policy dictates that the bank representative’s app must stay blocked until credit checks are complete. You need to display a model-driven app while credit checks run to ask the bank representative and client to wait for the credit check to complete. Which function should you use?
Answer options
A: Xrm.Navigation.openWebResource("prefix.myPoliteMessage.html")
B: Xrm.Navigation.openAlertDialog(myPoliteMessage)
C: Xrm.Utility.openWebResource("prefix_myPoliteMessage.html")
D: Xrm.Utility.showProgressIndicator(myPoliteMessage) Correct answer
Correct Answer:
D. Xrm.Utility.showProgressIndicator(myPoliteMessage)
Explanation

The requirement is to block the user interface while a long-running operation completes and display a waiting message. The Xrm.Utility.showProgressIndicator(message) function is specifically designed for this scenario. It displays a modal progress dialog with a custom message, which prevents the user from interacting with the application. The dialog remains active, blocking the UI, until the Xrm.Utility.closeProgressIndicator() function is called, typically after the asynchronous credit check process has finished. This directly meets the bank's policy to block the app and inform the user.

Why Incorrect

A. Xrm.Navigation.openWebResource("prefix.myPoliteMessage.html") This function opens a web resource, but it does not modally block the underlying form, allowing the user to continue interacting with the app.
B. Xrm.Navigation.openAlertDialog(myPoliteMessage) This displays a modal alert box, but it is designed for simple user confirmation and is closed by user action (clicking 'OK'), not by a background process completing.
C. Xrm.Utility.openWebResource("prefixmyPoliteMessage.html") This function opens a web resource in a new, non-modal window, which fails the requirement to block the user from interacting with the main application form. ---

References

1. Microsoft Docs - Xrm.Utility.showProgressIndicator: "Displays a progress dialog with the specified message. This dialog blocks the user from interacting with the app. You must use the closeProgressIndicator method to close the dialog."

Source: Microsoft, Power Apps model-driven apps developer documentation, "Client API reference > Xrm.Utility > showProgressIndicator".

2. Microsoft Docs - Xrm.Navigation.openAlertDialog: "Displays an alert dialog containing a message and a button... The dialog is modal and blocks the user from interacting with the app until it's closed." While modal, its purpose is for alerts requiring user dismissal, not for indicating an ongoing process that is closed programmatically.

Source: Microsoft, Power Apps model-driven apps developer documentation, "Client API reference > Xrm.Navigation > openAlertDialog".

3. Microsoft Docs - Xrm.Utility.openWebResource: "Opens an HTML web resource in a new window." This method is explicitly non-modal and does not block the originating window.

Source: Microsoft, Power Apps model-driven apps developer documentation, "Client API reference > Xrm.Utility > openWebResource".

Scroll to Top