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

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.

SQL Server Reporting Services

Controller class

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.

Maintain referential integrity with other tables.

Box 1: a table extension for Vendors and relation for the Vendor exclusions

Box 2: RelationShip Type

Scenario:

Users must be presented with a warning message before a direct delivery purchase order is created for a vendor in exclusion list.

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.

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