MB-500 Exam Dumps - Microsoft Dynamics 365: Finance and Operations Apps Developer

Scenario: Implement the Excel integration for the Vendor Exclusion List form.

B: By opening entity data in Excel, you can quickly and easily view and edit the data by using the Excel add-in.

SQL Server Reporting Services

Controller class

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.

Scenario: 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.

Scenario: You must develop a process to import payroll journals into the system.

A: Data Contract: Data contract class is the model class defining attributes needed for batch operations. These attributes are provided by the user, in a dialog. DataContractAttribute attribute is needed for the class and the properties methods requires DataMemberAttribute attribute.

C: Service: Service class extends from the SysOperationServiceBase class and contains the business logic for the batch operation. Developers often tend to add the business logic in controller classes, which violates the Single responsibility principle.

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

Box 1: Table extension

Isolate all new vendor exclusion codes as a new assembly by creating a table named VendExclusions.

Implement the Excel integration for the Vendor Exclusion List form.

The table extension object allows you to add additional fields or to change some properties on a table provided by the Dynamics 365 Business Central service. In this way, you can add data to the same table and treat it as a single table.

Box 2: Unique key

Create an index for the table named PrimaryIdx that uses the following fields: CustAccount, ItemId, VendAccount.

Box 3: Build and synchronize the database.

A project property lets you specify that the synchronize operation for the database should be performed every time that you build the project. This can be useful when you’re making changes to the table structure for an application. Each time that you build, you will know that the database is synchronized with the tables as they are defined in the project.