Explanation:
Step 1: In Solution Explorer, drag the CustTable form into the project.
Step 2: In The Application Object Tree (AOT), right-click the CustTable form.
Step 3: Select Create extension.
Note: To create an extension (in general terms), follow these steps:
* In the Application Explorer window, expand the AOT node.
* Expand the node for the element that you want to extend. For example, in Classic view, extend the Data Models node, and then extend the Tables node to view all available tables.
* Right-click the element that you want to extend.
* Select Create extension to add an extension to your current project. Select Create extension in new project if you want to add the extension to a new project. The element will be added to a project in the Solution Explorer window, and it will open in the element designer.
Reference:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-extension-example

Explanation:
Box 1: One, Two, Four, Fire
The statements in the finally clause are executed when control leaves the try block, either normally or through an exception.
Box 2: One, Three, Four, Five
Box 3: One, Three
Return ends the call.
Box 4: One, Three, One, Two, Four, Five
Retry restarts the try statement.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-ref/xpp-exceptions

Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/indexes/clustered-and-nonclustered-indexes-described

Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/build-consuming-data-entities

Explanation:
Step 1: Create a new import project.
Step 2: Specify the project category for the import.
Step 3: Specify the Source Data Format.
Step 4: Specify the target entity.
Step 5: Import the source file to the project.
The import process is done through the Import tile in the Data Management workspace.
Import a data package
1. Log into the environment using a login with sufficient privileges (typically this is the Administrator role).
2. On the dashboard, click the Data Management workspace.
3. Click the Import tile.
4. On the next page, do the following:
Provide a name.
In the Source Data Format field, select Package.
Click the Upload button and choose the appropriate package file from the location for the data being imported. This will import all the files from the package.
Click Save, and then click Import.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/data-entities-data-packages

Explanation
Weight data can be maintained with a maximum of two decimals by default. If you require the ability to enter, maintain, and view weight data with a maximum precision of six decimals, you must extend the decimal point precision for the WeightBase extended data type.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/decimal-point-precision

Explanation
* In Microsoft Visual Studio, on the Dynamics 365 menu, click Model Management > Refresh Models.
* Open Application Explorer by clicking View > Application Explorer.
* Right-click the AOT root node, and then click Model view.
A list of installed models is displayed.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/manage-runtime-packages

Explanation:
The following illustration shows the elements of role-based security and their relationships.

Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/role-based-security

A: You must create a class.
D: Extension lets you extend existing artifacts in a new model.
A model that contains only extension customizations can be compiled into its own assembly and be deployed in its own package.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/class-extensions
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/model-split

You can only set the new String size to a value equal to or larger than the base EDT value.
Incorrect Answers:
B, C: You can only modify the value if the EDT does not extend from another EDT.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/modify-edt

Explanation/Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/modify-properties

You would need to use the on-click property of the command button.
Reference:
https://support.microsoft.com/en-gb/office/use-a-command-button-to-start-an-action-or-a-series-of-actions-c7bf2827-2f3e-42b8-83d6-6c4f0de78990
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/user-interface/action-controls

Explanation:
Box 1: element.runAsynch
Box 2: container
Reference:
https://devblog.sertanyaman.com/2017/03/14/synchronous-and-asyncronous-operations-in-ax7/

Explanation:
Step 1: Synchronize the database
Entities are created as views in Microsoft SQL Server, and staging tables are also added. Therefore, you must sync a database when you build entities.
Step 2: Build the solution
Build your project
In Solution Explorer, right-click your project, and then click Properties.
Change the value of the Synchronize database on build property to True, and then click OK. This property must be set only one time per project.

On the Visual Studio toolbar, click Build > Build Solution to build the project.
Step 3: Configure properties for the data entity
After build visually validate and customize an entity
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/build-consuming-data- entities

Explanation:
Box 1: package
An AOT package is a deployment and compilation unit of one or more models that can be applied to an environment. It includes model metadata, binaries, reports and other associated resources. One or more AOT packages can be packaged into a deployable package, which is the vehicle used for deployment of code (and customizations) on demo, sandbox, and production environments.
Box 2: New model
Model – You configure your model to refer to two other models. This enables your model to reference metadata and code elements that are in other packages.
Box 3: project
Project – You create a project and then associate your project to your new model. You add elements to your project, which are also added to your model. Specifically, you add an extended data type (EDT). You also add a table that you populate with fields and a method.
Box 4: deployable package
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/create-data-model-elements

Explanation

Box 1: User Acceptance Testing (UAT) and Build
Box 2: User Acceptance Testing (UAT) Only
Not all environments contain all the tools. The following table shows the tools that are available for each type of environment.
Box 3: Build only
Reference:
http://axhelper.com/?p=16527

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.
1. In the extension model, create a form extension for the selected form.
2. 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

Example of Restricted
Suppose we have two tables (Customer & Order) and the relation is of One-To-Many i.e Customer can have many orders.
So on a parent table i.e.(Customer) if I set a delete action property to “RESTRICTED” for Order table. Then If I go and delete the record from a Customer table. It will first check the record in the child table and if exist that warning prompt saying that first we need to delete a record from child table.
Incorrect Answers:
B: Example of Cascade:
Suppose we have two tables (Customer & Order) and the relation is of One-To-Many i.e. Customer can have many orders.
So on a parent table i.e.(Customer) if I set a delete action property to “CASCADE” for Order table. Then If I go and delete the record from a Customer table. It will also delete all the related records in Order table automatically.
C: Example of Cascade + Restricted
Suppose we have three tables (Person ,Customer & Order) Now Person is a parent of Customer table, and Customer is a parent of Order table having (One-To-Many) relations If I set a Delete action property on Person table to “CASCADE” for customer table and If I set a Delete Action property on a CUSTOMER table for Order table to “CASCADE +RESTRICTED”.
So if I delete a record from Customer table then It will first check the record in the child table(order table) and if exist that warning prompt saying that first we need to delete a record from child table.
But if I delete a record from Person table it will automatically delete a record in Customer table and all records related to customer table in Order table would also be deleted.
Reference:
https://amazingax.wordpress.com/2013/01/13/microsoft-dynamics-ax-2012example-of-cascaderestricted-and- cascade-restricted-delete-action-property-for-a-table-relation/ Developer Tools Testlet 1 Case study 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. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. 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
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 BI 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.
Requirements
General
* You must configure a cloud-based Dynamics 365 Finance development environment and enable code extension 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 VendExclusions.
* Create an index for the table named PrimaryIdx that uses the following fields: CustAccount, ItemId, 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.
Developer2 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.

Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-started/personalize-user-experience