Explanation:
Graphical user interface, text, application, email Description automatically generated

Explanation:

Scenario: CashDisc form
You must extend the CashDisc form to add a new field named MinimumInvoiceAmount to the form. You must add a new Extended Data Type to the extension model for the new field. The new field must be added above the discount method field. The field must display 10 characters.
Box 1: extension
To add a new field to an existing table, you must first create a table extension.
Box 2: field
Box 3: field group
Box 4: data source
Often, the information that is stored in existing tables doesn't satisfy customer requirements. Therefore, additional tables must be created, and data from those tables must be shown on pages.
You can add new data sources to existing forms through extension. Follow these steps.
In the extension model, create a form extension for the selected form.
Right-click the form extension, and then select New Data Source.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/add-datasource
Topic 2, World Wide Importers
This is a case study Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment and problem statements. When you are ready to answer a question, click the Question button to return to the question.
Background
Wide World Importers sell office supplies, furniture, and fittings to their customers across the United States.
The company has the following locations:
* a retail store in Seattle
* a warehouse in Seattle
* a customer support and call center in Atlanta
* a team of field workers that provide furniture installation services at customer sites Wide World Importers plans to implement Dynamics 365 Finance and Microsoft Azure cloud platform features.
Current environment
Requirements
Customers may place orders by email, phone, or by using the company's website. The company authorizes and processes credit card transactions by using a web-based application. Customer, inventory, supplier, and other master and transactional data is stored in a legacy database.
The company collects feedback from customers by phone or a form on the company's website and maintains the data in a Microsoft Excel workbook.
Wide World Importers runs on-premises applications to manage payroll and workers compensation. The company has a set of Microsoft Power Bl dashboards that present data from a reporting database.
The company creates a Lifecycle Services (LCS) implementation project and completes Dynamics 365 Finance onboarding.
The company maintains production, quality assurance (QA). development, user acceptance testing (UAT), and build environments.
General
* You must configure a cloud-based Dynamics 365 Finance development environment and enable code extensions that support updates.
* You must configure version control and a Build environment.
* You must migrate all legacy data to the new system.
* You must implement best practices for X++ coding, the data model, caching, and security.
* All new code must be unit tested in a development environment and then validated by the QA team before code is added to source control.
Business processes
* You must configure vendor trade agreements.
* Products must be shipped directly from suppliers to customers depending on customer location to save indirect costs.
* You must collect customer feedback on products shipped directly from vendors.
* You must deploy code to a UAT environment for testing before deploying code to production.
* You must validate all entries for the purchase order creation form.
* You must develop a web portal that allows customers to browse products, place orders, and check order status. Product data for the web portal must be integrated as periodic batches.
Business systems
* You must install and configure a third-party solution for credit card processing within Dynamics 365 Finance. The third-party company will provide a deployable package.
* The workers compensation application must be able to call an API to update worker compensation details in Dynamics 365 Finance.
* You must develop a process to import payroll journals into the system.
* You must configure the warehouse mobile device portal for warehouse operations.
* You must install a third-party solution to support web portal integration. The solution is supplied as a source code model file.
Vendor exclusion list
You must develop a new solution to maintain a Vendor exclusion list for each customer and item combination.
The solution must meet the following requirements:
* Isolate all new vendor exclusion codes as a new assembly by creating a table named Vend Exclusions.
* Create an index for the table named Primaryldx that uses the following fields: CustAccount, Itemld, VendAccount.
* Ensure that users can open the Vendor Exclusion list report from the customer master form. The list must display the customer account Item ID, and Vendor account fields.
* Implement the Excel integration for the Vendor Exclusion List form.
* Provide functionality to periodically export the Vendor exclusion list to prepare reports by using standard reporting capabilities of Dynamics 365 Unified Operations.
* Develop necessary security permissions to view and maintain the new Vendor exclusion list functionality and reporting. Users with maintain rights will be able create, update, and delete the exclusion list. Permissions must be assigned to security roles to match company security model.
* Maintain referential integrity with other tables.
* Users must be presented with a warning message before a direct delivery purchase order is created for a vendor in exclusion list.
* Sales managers must be alerted when a new exclusion record is added to the system.
Security
* You must implement the record level audit feature to identify the users who created the record.
* Grant specific users rights to maintain the vendor exclusion list by using Excel.
* You must implement validation to check whether a proposed direct delivery purchase order vendor is on the exclusion list for the customer and product combination.
Issues
User1 is not able to access many features in the system. You must provide User1 administrator rights.
A sales manager suspects a data-related issue in the vendor exclusion list. User1 must identify the user who created the referenced exclusion records.
Developed joins the company and does not have access to a development environment or source control.
User2 reports performance issues when they generate direct delivery purchase orders after current updates are applied.
User2 reports that they cannot access new functionality and reports.

The SysTest framework now supports the major test attributes in the adaptor to be on par with the MSTest framework adaptor. This includes attributes like Category, Owner, Priority, and Test Property.
Note:
The Priority attribute SysTestPriority, which requires an integer value, is now available. A priority can only be specified once, but is supported on both the class and method level, with method level taking precedence over class level.
The Owner attribute, SysTestOwner, has also been added. This attribute was technically already supported for filtering in the Test Toolbox window, but the attribute itself was missing in X++. Similar to Priority, an owner can only be specified once and is supported on both the class and method level, with the method level taking precedence.
SysTestProperty specifies a property and a value (two strings), and can now be used in the Test Toolbox window in Visual Studio. Test Property can be specified multiple times, and can exist on both the class and method level.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/perf-test/systest-filtering

Explanation

Box 1: Yes
Class extension - Method wrapping and Chain of Command.
The functionality for class extension, or class augmentation, has been improved. You can now wrap logic around methods that are defined in the base class that you're augmenting. You can extend the logic of public and protected methods without having to use event handlers. When you wrap a method, you can also access public and protected methods, and variables of the base class. In this way, you can start transactions and easily manage state variables that are associated with your class.
Box 2: Yes
In the following example, the wrapper around doSomething and the required use of the next keyword create a Chain of Command (CoC) for the method. CoC is a design pattern where a request is handled by a series of receivers. The pattern supports loose coupling of the sender and the receivers
[ExtensionOf(classStr(BusinessLogic1))]
final class BusinessLogic1_Extension
{
str doSomething(int arg)
{
// Part 1
var s = next doSomething(arg + 4);
// Part 2
return s;
}
}
Box 3: Yes
Instance and static methods can be wrapped by extension classes. If a static method is the target that will be wrapped, the method in the extension must be qualified by using the static keyword.
Box 4: No
Wrapper methods must always call next.
Note: Wrapper methods in an extension class must always call next, so that the next method in the chain and, finally, the original implementation are always called. This restriction helps guarantee that every method in the chain contributes to the result.
In the current implementation of this restriction, the call to next must be in the first-level statements in the method body.
Here are some important rules:
Calls to next can't be done conditionally inside an if statement.
Calls to next can't be done in while, do-while, or for loop statements.
A next statement can't be preceded by a return statement.
Because logical expressions are optimized, calls to next can't occur in logical expressions. At runtime, the execution of the complete expression isn't guaranteed.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/method-wrapping-coc