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

Correct Answer: CD

Reference: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/validations-defaults-unmapped-fields https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/method-wrapping-coc

Correct Answer: A

Class extension - Method wrapping and Chain of Command

Wrapper methods must always call next (not B)

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. (not D)

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.

Incorrect:

Not B: Need to use the next keyword.

Not C: Use the if-statement before the next-statement to prevent the standard code to run.

Not D: Calls to next can't be done conditionally inside an if statement.

Reference:

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/method-wrapping-coc

Correct Answer: D

Example, Create additional Fleet Management extensions

This section shows how you can use the Visual Studio tools to create and interact with extensions.

Example, Extend the FMVehicle Table

1.

In Solution Explorer, select the FleetManagement Discounts project.

2.

In Visual studio, in Application Explorer, select View > Application Explorer, and search for the table named FMVehicle. Type FMVehicle type:Table in the filter bar and press Enter.

3.

Right-click FMVehicle, and then select Create extension.

An extension of the FMVehicle table is created in the FleetManagement Discounts project named FMVehicle.Extension.

..some details omitted..

4.

Expand the Events node. The Events node lists all events that the table exposes. This list includes events that are defined by the framework, and delegate methods that are defined by application developers.

Note

Different framework events are exposed on the designers of many types of element and sub-elements, like table events, form events, form data source events, and form control events.

5.

Right-click onInserting, and then select Copy event handler method.

6.

Etc.

Note: Munson's Pickles and Preserves Farm is currently in the process of adding the other required fields: one for Product Name and one for Batch ID. The new fields must be related to extended data types for the original fields on the existing data source for the Inventory Status form. Munson's Pickles and Preserves Farm plans to add the EcoResProductName and Batch ID data to the extended table for WHSTmpStatusChange. The fields on the table extension must be populated with data and visible on the Inventory Status form on insert.

Reference: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/customize-model-elements-extensions