nerdexam
Microsoft

MB-500 · Question #299

Case study 4 - ADatum Corporation Background ADatum Corporation is a market leader in the design and distribution of innovative aluminum systems. The company provides services to the architectural…

The correct answer is A. Details master C. Simple List. Scenario: Requirements. Business processes A process named Populate check data must be designed based on the following: The process must run from the All customers list page and populate a custom table named CustCheckData with 1000 rows. The table must have two fields named…

Design and develop AOT elements

Question

Case study 4 - ADatum Corporation Background ADatum Corporation is a market leader in the design and distribution of innovative aluminum systems. The company provides services to the architectural, residential, industrial, and home improvement markets in Australia. The company has warehouses in Perth. Sydney, and Melbourne. A team of warehouse employees provides delivery to the customer sites. Current Environment ADatum Corporation currently uses Microsoft Dynamics AX 2009. Customers use email or phone calls to place orders. After the company provides a quote to customers, the customer must agree to the sale price before the company places a sales order. The company is migrating to Dynamics 365 Finance and Dynamics 365 Supply Chain Management using a phased rollout strategy to its sites. The company has the Lifecycle services project to manage various environments and releases. The company has the following Finance and Supply Chain Management environments: - Development - Quality assurance (QA) - User acceptance testing (UAT) - Production The company uses Azure DevOps for a code repository. All developers use a development branch to check in code and a release branch to maintain the code for production releases. Requirements. General - Configure a cloud-based development environment for Finance and Supply Chain Management. Enable a code extension that supports updates. - Configure Microsoft-supported version control and an Azure-hosted build pipeline. - Migrate all document handling attachments for the customers to Finance and Supply Chain Management from Dynamics AX 2009. - Audit X++ code for a best practice check. - All new code must be unit tested in a development environment and then validated by the QA team before the code is merged into the Release branch for further releases. Requirements. Business processes - All changes that are deployed to the UAT environment must be approved for code release to production. - The sales manager requires a solution that is extensible to ensure that new master tables document handling attachments are migrated to the new system. - A base class named MigrateAttachment must be designed with methods that all child classes must implement. - A method named processAttachment must be created so that extenders are not able to subscribe to pre-events and post-events. - On the All sales orders list page, two new fields must be added for the total sales order amount. One field uses goods and services tax (GST) and the other field does not use GST. - A process named Populate check data must be designed based on the following: The process must run from the All customers list page and populate a custom table named CustCheckData with 1000 rows. The table must have two fields named CheckNumber and BankNumber. The process must return to the current session after the data is processed. - The generated check data must be available for users to access in a tabular form without additional details and preview panes. - The purchase manager requires a new data entity to send out the information for purchase order inquiries that are generated in Finance and Supply Chain Management - The sales manager must be able to access the total quotation for the sites and item types. - The sales manager requires a quotation number to be printed on the sales invoice business document. Customers must be able to access the reference number on the invoice documents. - The purchase manager requires a new approval workflow for approving purchase orders that are more than $10,000. Requirements. Business systems - After a user named UserA posts a packing slip for a sales order, customers must be informed of the product delivery in real-time. This information is provided using business events. - Purchase order inquiries must be exported from the Finance and Supply Chain Management using data packages. Users must be able to query using OData but should not be able to update or create the data in the system. - A sales manager's workspace must display the total quotations using key performance indicators. - The purchase order approval workflow must be configured from the procurement and sourcing module. Issues - UserA reports delays when opening the All sales orders list page. - A customer is unable to access the business events for a packing slip that is posted by UserA. - A user named UserB reports that the system is unresponsive when they run the Populate check data process for a customer. - UserA reports that the print management settings in the accounts receivable module do not display the new layout when testing a new sales invoice report layout in the UAT environment. You need to design a form to display the check data. Which two form patterns can you use? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.

Exhibit

MB-500 question #299 exhibit

Options

  • ADetails master
  • BSimple List and Details
  • CSimple List
  • DList page

How the community answered

(47 responses)
  • A
    77% (36)
  • B
    6% (3)
  • D
    17% (8)

Explanation

Scenario: Requirements. Business processes * A process named Populate check data must be designed based on the following: The process must run from the All customers list page and populate a custom table named CustCheckData with 1000 rows. The table must have two fields named CheckNumber and BankNumber. The process must return to the current session after the data is processed. *-> The generated check data must be available for users to access in a tabular form without additional details and preview panes. A: Details Master form pattern A details form is the primary method for entering data. A details form is the primary method for entering data. These forms let the user view, edit, and act upon data. All content on these form types is structured into FastTabs that can be expanded and collapsed, so that multiple FastTabs can be open at the same time. The FastTabs can contain fields or a grid, and each FastTab can have a local toolbar. Two patterns are described in this Detail Master - This is the basic Detail Master pattern. This is the pattern that you should use by Detail Master w/ Tabs - You should use this pattern when an entity requires many FastTabs (more than 15) that can be grouped into categories. In both cases, the grid view is structured the same. C: Simple List form pattern This pattern is used to maintain data for simple entities. The Simple List pattern is used to maintain data for simple entities. Simple entities are entities that have six or fewer fields and no parent/child relationships. There are some exceptions where entities that have up to 15 fields are still considered simple entities. * List Page form pattern A list page presents a set of data on a UI that is optimized for browsing records, so that you can find and work with a specific record. A list page presents a set of data on a user interface that is optimized so that you can browse records, find the right record, and then take an action upon that record. The list page lets the user search, filter, and sort the data. FactBoxes on the right side of the grid show related data for the active record. Actions that are relevant to the record are located on the ActionPane at the top of the page. The use of this pattern is now discouraged when there is a 1:1 correspondence between the List Page and Details page. Current guidance is to use this pattern only in other situations, such as when list pages have no backing details pages or have multiple backing details page (for example, when project quotations and sales quotations are shown together in the same List Page). https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/user-interface/details- master-form-pattern https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/user-interface/list-page-

Topics

#form types#Details master#Simple List#AOT forms

Community Discussion

No community discussion yet for this question.

Full MB-500 Practice