MB-500 · Question #255
Drag and Drop Question A company uses Dynamics 365 Finance. The company needs to track deletions of purchase order header records only. You need to enable the change tracking. Which four actions…
The correct answer is Configure entity export to database on the Data management workspace.; Select Data entity list page from the Data management workspace and then select Change tracking.; Select the published entity and then select Change tracking.; Select the primary table option. Dynamics 365 Finance: Change Tracking for Purchase Order Headers Core Concept Change tracking in D365 Finance lets the system log when records are created, updated, or deleted. The setup follows a logical flow: configure the export framework → enable tracking on the entity →…
Question
Exhibit
Answer Area
Drag items
Correct arrangement
- Configure entity export to database on the Data management workspace.
- Select Data entity list page from the Data management workspace and then select Change tracking.
- Select the published entity and then select Change tracking.
- Select the primary table option.
Explanation
Dynamics 365 Finance: Change Tracking for Purchase Order Headers
Core Concept
Change tracking in D365 Finance lets the system log when records are created, updated, or deleted. The setup follows a logical flow: configure the export framework → enable tracking on the entity → specify what to track.
Why This Sequence
Step 1: Configure entity export to database on the Data management workspace
Why first: Change tracking in D365 requires the entity to be published to an external database via the Data management export framework. You cannot enable change tracking on an entity that hasn't been set up for export. This establishes the foundational connection between D365 and the target database.
Step 2: Select Data entity list page from the Data management workspace and then select Change tracking
Why second: Once export is configured, you navigate to the entity list to access change tracking settings. This is the entry point into the change tracking configuration UI - you cannot reach the tracking options without first going through this page.
Step 3: Select the published entity and then select Change tracking
Why third: From the entity list, you must identify and select the specific entity (Purchase Order Header in this case) and then click Change tracking. This scopes the configuration to the correct entity before choosing what to track.
Step 4: Select the primary table option
Why fourth/last: This is where you define the scope of tracking. The scenario requires tracking deletions of purchase order header records only - the primary table option tracks changes on the main/header table, not child tables. This is the most granular decision and logically comes after all navigation steps are complete.
Why the Other Items Are Excluded
| Item | Why Excluded |
|---|---|
| Select the database to export data to and then select Publish | This is part of initial export setup, but it's not one of the four required steps in this specific change tracking workflow path. |
| Select the Enable entire entity option | This would track all tables in the entity (header + lines), not just the header. Since the requirement is header records only, this option is incorrect for this scenario. |
Common Mistakes
- Choosing "Enable entire entity" is the most common trap. It sounds comprehensive, but it tracks everything - violating the "header records only" requirement. Always match the scope option to the business requirement.
- Skipping the export configuration - candidates sometimes jump straight to the entity list, forgetting that change tracking depends on the export-to-database framework being set up first.
- Confusing the order of Steps 2 and 3 - Step 2 gets you to the entity list, Step 3 selects the specific entity. The navigation is hierarchical, so they cannot be reversed.
Topics
Community Discussion
No community discussion yet for this question.