PL-400 · Question #184
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…
The correct answer is A. Yes. This third variant in the series also meets the stated goals. The solution likely uses a slightly different but equally valid mechanism - such as passing the contact type via the NavigateTo API with customParameters, or using a different formContext method to read the parameter…
Question
Options
- AYes
- BNo
How the community answered
(35 responses)- A71% (25)
- B29% (10)
Explanation
This third variant in the series also meets the stated goals. The solution likely uses a slightly different but equally valid mechanism - such as passing the contact type via the NavigateTo API with customParameters, or using a different formContext method to read the parameter on load. Both Xrm.Navigation.openForm with extraqs and the newer Xrm.Navigation.navigateTo with custom parameters are supported methods to pass data between forms in model-driven apps. As long as the Contact form's JavaScript correctly reads the parameter and applies the appropriate form layout (via formContext.ui.setFormNotification or switching the active form), the requirement is satisfied and the answer is Yes.
Community Discussion
No community discussion yet for this question.