Drag and Drop Question You create a Power Apps app to display customer feedback. You need to submit and display customer feedback for each sales order. In which order should you perform the actions?…

Question

Exhibit

Answer Area

Explanation

Embedding a Power Apps App in a Dynamics 365 Sales Order Form

This question tests your knowledge of the workflow for embedding a Power Apps canvas app into a model-driven app form (Dynamics 365).

Correct Order & Why

1. Configure and embed the app

This must come first because the Power Apps app needs to exist and be configured before it can be placed anywhere. In D365 Finance & Operations, this means setting up the canvas app (setting the App ID, entity context, size, etc.) so it is ready to be embedded. You cannot reference or place something that hasn't been prepared yet.

Common mistake: Thinking you should navigate to the form first. You have nothing to embed yet - the app configuration must precede placement.

2. Navigate to the Sales order form

After the app is configured, you go to the specific form where you want it to appear. Personalization in D365 is page-context dependent - you must be on the target form to personalize it. There is no way to add a Power Apps embed to a form you are not currently viewing.

Common mistake: Assuming you can personalize from a central admin panel without being on the target form. D365 personalization is done in-place.

3. Personalize the page

While on the Sales order form, you open the Personalization toolbar and add the previously configured Power Apps app as a new tab or section. This step embeds it visually into the form layout for the current user (or can be pushed to all users via saved views/admin personalization).

Common mistake: Doing this before navigating to the form, or before the app is configured. Both would prevent successful embedding.

4. Refresh the browser

After saving the personalization, a browser refresh is required for the embedded app to fully load and render in its new position. This is a standard D365 behavior - personalization changes are saved server-side and reloaded on refresh.

Common mistake: Expecting changes to appear instantly without a refresh, or placing this step before personalization is saved.

Summary

The key mental model: build → find → place → view. Each step enables the next.

No community discussion yet for this question.