You are developing a customization for Dynamics 365 Finance. The customization must extend objects from the Application Foundation package. You need…

When creating a new model for a customization in Dynamics 365 Finance, two fundamental configuration steps are required. First, for proper application lifecycle management (ALM), the new model should be created in a new package. A package is the unit of compilation and deployment, and creating a new one ensures the customization is built into its own separate assembly, isolating it from standard code and other customizations (A). Second, to extend objects from an existing package, such as Application Foundation, the new model's package must have a direct reference to it. This dependency is mandatory for the compiler to recognize and allow interaction with the objects from the Application Foundation package (B).

C. Creating a model as part of an existing standard package is contrary to the extension-based customization model and is prevented for sealed, standard packages.

D. While assigning the model to the USR layer is a correct and necessary step in the creation wizard, establishing the package structure (A) and its dependencies (B) are more fundamental to enabling the required extension.

E. Creating an extension class is a development task performed within the model after it has been created and configured. It is not a step in the creation or configuration of the model itself.

1. Microsoft. (2023). Create finance and operations models in Visual Studio. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/create-models.

Section: "Create a new model": This document outlines the steps in the "Create model" wizard. Step 3, "Select Create new package," directly supports option A, stating, "A new package is compiled into its own assembly." Step 4, "Select the packages that the new model will have dependencies on," directly supports option B, explaining that you must select the packages you intend to extend.

2. Microsoft. (2023). Models, layers, and packages. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/models-layers-packages.

Section: "Packages": This section clarifies that "A package is a deployment and compilation unit of one or more models." This reinforces the concept in option A that creating a new package results in a separate, deployable assembly.

Section: "Model references": This section states, "If you want to use elements from another model, you must add a reference to that model." This confirms the necessity of referencing the Application Foundation package, as described in option B.