MB-230 · Question #441
Drag and Drop Question A company requires the following Dynamics 365 Customer Service enhancements: - Submit new Knowledge articles from the case form. - Provide a full screen of service operations…
The correct answer is Canvas app; Custom page; Canvas app. Dynamics 365: Canvas App vs Custom Page - Explained The Core Distinction | Feature | Canvas App | Custom Page | |---|---|---| | Where it lives | Embedded inside a model-driven form | Full-screen page within the model-driven app | | Context awareness | Receives parameters from…
Question
Drag and Drop Question A company requires the following Dynamics 365 Customer Service enhancements:
- Submit new Knowledge articles from the case form.
- Provide a full screen of service operations for the organization.
- List any warranty claims from a third-party system for the selected
case product. You plan to use embedded canvas apps and custom pages to meet the requirements. You need to implement the solution for each requirement. Which solutions should you use? To answer, move the appropriate solutions to the correct requirements. You may use each solution once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Answer:
Exhibit
Answer Area
Drag items
Correct arrangement
- Canvas app
- Custom page
- Canvas app
Explanation
Dynamics 365: Canvas App vs Custom Page - Explained
The Core Distinction
| Feature | Canvas App | Custom Page |
|---|---|---|
| Where it lives | Embedded inside a model-driven form | Full-screen page within the model-driven app |
| Context awareness | Receives parameters from the host form (e.g., record ID) | Standalone navigation destination |
| Use case | Augmenting a specific record's form | Replacing/providing a full app-level view |
Placement Breakdown
Requirement 1 → Canvas App "Submit new Knowledge articles from the case form"
The phrase "from the case form" is the trigger. A canvas app can be embedded as a control directly on the case form, allowing the user to author and submit Knowledge articles without leaving the case record. It can receive the case context (e.g., case ID) as a parameter. A custom page cannot be embedded inside a form - it's a full-page destination.
Requirement 2 → Custom Page "Provide a full screen of service operations for the organization"
"Full screen" and "for the organization" are the triggers. Custom pages are designed precisely for full-page, full-screen experiences within a model-driven app. They are added to the sitemap as navigation items and render as a complete page. This is not record-contextual - it's an organizational dashboard/view. Using a canvas app here would force awkward full-page embedding hacks; custom pages are the native solution.
Requirement 3 → Canvas App "List warranty claims from a third-party system for the selected case product"
Two clues here:
- "third-party system" - Canvas apps have rich connector support to external data sources (REST APIs, SQL, etc.)
- "for the selected case product" - the app needs record context (the product on the case), which is passed as a parameter to an embedded canvas app on the case form
A custom page has no mechanism to receive the currently selected case product as context in the same embedded manner.
Common Mistakes
- Mixing up "full-screen" triggers: Candidates often assign Canvas App to Requirement 2 because canvas apps are visually flexible. The key is that custom pages are the architecturally correct full-screen solution inside model-driven apps.
- Thinking custom pages can embed in forms: They cannot. Custom pages are navigation-level, not form-control-level.
- Overlooking context passing: Requirements that reference "the selected [record]" strongly imply an embedded canvas app, since it can receive the host form's record ID as an input parameter.
Topics
Community Discussion
No community discussion yet for this question.