From a JavaScript command on the account form, a developer must open a custom page named contoso_creditreview_7b2c1 as a centered modal dialog that receives the current account's ID. Which Client API call does this?
Select an answer to reveal the explanation.
Short Explanation
navigateTo is your travel agent: tell it the destination is a custom page, give it the record you're carrying, and say you want a dialog in the middle of the screen. The other calls book you to the wrong place, a form or a web resource window.
Full Explanation
Xrm.Navigation.navigateTo accepts a page input and navigation options. For a custom page the page input uses pageType custom, name set to the custom page's logical name, and optionally entityName and recordId, which the page can read to know which record it was opened for. The navigation options set target to the dialog value and position to center, and can specify width and height; the call returns a promise that resolves when the dialog closes, so the form can refresh afterward. openForm opens a table form for a record or a new record, and a custom page is not a table, so passing its name as entityName does not open it. openWebResource opens an HTML web resource in a new browser window; custom pages are not web resources and cannot be opened that way. Using pageType entityrecord tells the platform to open a record form, and an inline target navigates the main area rather than showing a modal dialog, so neither part matches the requirement. Exam caveat: the custom page must be added to the model-driven app before navigateTo can open it, otherwise the call fails at runtime. Operational check: run the command on an account, confirm a centered modal opens, and confirm the page shows the account passed in recordId.