Question
Case Study 3 - Munson's Pickles and Preserves Farm Background Munson's Pickles and Preserves Farm produces and sells jarred food goods. The organization has several production and warehouse locations across the United States. Each location runs both production and warehousing operations. The company has three locations: East, Central, and West. The company is upgrading its Dynamics AX 2009 system to Dynamics 365 Finance. Current environment General Munson's Pickles and Preserves Farm plans to migrate customizations, data, and integration from its legacy system into Dynamics 365 finance and operations apps. The Dynamics 365 finance and operations environment includes: - multiple cloud-hosted development environments using Microsoft Visual Studio 2017 - a Microsoft Azure DevOps project for source control - two tier 2 environments for user acceptance testing and staging, as well as production Munson's Pickles and Preserves Farm is currently in the planning and development phase of the upgrade process. The company's internal development team needs additional development resources to address issues. The company already created a project that is set up to use a custom model named GPExtensions. Integrations Munson's Pickles and Preserves Farm has a new integration for its freight processing information. The internal development team created the secure file transfer protocol (SFTP) site for the source information to be stored and the staging table to house the source information once the data is added to Dynamics 365 Finance. Information from the source will be transferred once a day from the source system and integrated with the target system. More than 10,000 records will be transferred over the integration. The company created an aggregate entity for the integration to minimize the amount of transmitted data. Munson's Pickles and Preserves Farm has added a new integration for freight processing where all item weights, dimensions, and other factors will be configured in the external portal while planning the loads. Once the load is planned, it will be integrated into Dynamics 365 finance and operations apps for the freight invoice processing to occur. No duplicate invoices or posting are associated with the freight invoice charges. The integration of this information from the source system is intended only for report creation and compilation purposes. Planned changes Munson's Pickles and Preserves Farm wants to change inventory forms to fit its current needs. Any modifications or enhancements must follow the existing functionality for forms in Dynamics 365 Finance. Requirements Integrations All data from integrations have the same format as an existing Dynamics 365 Finance apps field. All enhancements or customizations must use existing assets before creating new functionality. Munson's Pickles and Preserves Farm wants to change its integration strategy to include real- time data from the freight processing source system. The inventory must update as it is sold from the system. That information will be updated in Dynamics 365 Finance. The freight processing integration requires the use of an SFTP site to store XML files from the source system. The additional integration will use OData and must be transferred in real time. A periodic batch job must: - Pull data from the SFTP site. - Import the data to a staging table used to hold the information from the source system. - Map source data to the target table in Dynamics 365 Finance. The imported Load ID field must be added to the Sales Order header for all processed orders. Additional requirements for integrations, including other integration strategies, may be necessary as the company grows. Existing tables must be changed to include the Load ID. The database will need to be synched before adding the Load ID field. Changes Munson's Pickles and Preserves Farm must change the Inventory Status form to include more columns. It plans to create a table to enter the data for the Inventory Status form as a new data source. The company wants to add both the Product Name field and Batch ID field to this new table. The current form includes the item number, location, license plate, product inventory dimensions, and quantity. The grid on the Inventory Status form must include the product name by using the item number and legal entity. The user interface must be created to include the new columns and the data must be available to add to the grid. The form must have only an Action Pane, a Navigation List, a List Style Grid, a Details Header, and a Details Tab in the design and include the Load ID field. Munson's Pickles and Preserves Farm is currently in the process of adding the other required fields: one for Product Name and one for Batch ID. The new fields must be related to extended data types for the original fields on the existing data source for the Inventory Status form. Munson's Pickles and Preserves Farm plans to add the EcoResProductName and Batch ID data to the extended table for WHSTmpStatusChange. The fields on the table extension must be populated with data and visible on the Inventory Status form on insert. Issues - The internal development team has created the SFTP site connections, the staging table, and the batch jobs for the new integration for freight processing. The development team needs to map the source data to the target table and the data management workspace. The development team notices errors with mapping target fields in the data management workspace. The team needs another developer to configure the table extensions, class extensions, and form extensions that are required for the planned changes. - The internal development team has issues adding the required fields to the Inventory Status standard form. The team needs another developer to configure the table extensions, class extensions, and form extensions that are required for the planned changes. Question Drag and Drop Question You need to map the target data fields in the Data management workspace for the custom data entity. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. Answer:
Explanation
Explanation: Mapping Target Data Fields in Data Management Workspace
Important Context Note
There is a mismatch in this question as presented: the question asks about mapping target fields in the Data Management workspace, but the answer items describe integration configuration properties. This is a common issue with extracted exam questions. The items actually describe the configuration sequence for setting up the integration job itself, which precedes or accompanies the mapping step. Work with the answer as given.
Why This Sequence: Asynchronous → Recurring Job → Real Time
1. Asynchronous
Chosen over: Synchronous
Technical reason:
The case study states more than 10,000 records will be transferred over the SFTP integration. In D365 Finance's Data Management workspace, you must choose a processing mode:
- Synchronous: Blocks execution and waits for the operation to complete. Only suitable for small data volumes where immediate confirmation is needed.
- Asynchronous: Submits the job to a batch queue and processes in the background without blocking. Required for large-volume imports.
10,000+ records exceeds the practical threshold for synchronous processing. Choosing asynchronous prevents timeouts and allows the system to remain responsive.
Common mistake: Choosing Synchronous because the data is "only once a day" - frequency is irrelevant; volume drives this decision.
2. Recurring Job
Chosen over: One Time Job
Technical reason:
The requirements explicitly state the SFTP integration must:
- Pull data from the SFTP site
- Import to staging table
- Map source data to target table
...and that information is transferred once a day. This is a periodic, ongoing operation. A recurring job runs on a defined schedule indefinitely, which matches this requirement.
A one-time job executes once and stops - useless for a daily operational integration.
Common mistake: Selecting One Time Job during initial setup/testing and forgetting to switch to Recurring for production. This is an extremely common real-world error.
3. Real Time
Chosen over: Non-Real Time
Technical reason:
The case study introduces a second integration requirement:
"The additional integration will use OData and must be transferred in real time."
"The inventory must update as it is sold from the system."
After configuring the SFTP batch job (steps 1–2), the configuration must also account for the real-time OData integration for inventory updates. Selecting Real Time ensures data is available in D365 Finance immediately upon transfer, satisfying the inventory accuracy requirement.
Non-Real Time would defer updates, which directly violates the requirement that inventory reflects sales immediately.
Common mistake: Assuming "real time" and "asynchronous" are contradictory - they are not. Asynchronous describes how the system processes the job internally; real time describes how quickly data must be available to end users after the source fires it.
Summary Table
| Position | Choice | Rejected | Deciding Factor |
|---|
| 1 | Asynchronous | Synchronous | 10,000+ record volume |
| 2 | Recurring Job | One Time Job | Daily recurring batch requirement |
| 3 | Real Time | Non-Real Time | OData inventory sync must be immediate |
