Elements, Models, and Packages: Structural Hierarchy in Visual Studio -Dynamics 365 F&O

Description: In this video, we dive into the structural hierarchy of elements, models, and packages in Visual Studio for finance and operations. Learn how elements are created and organized, how models contain multiple elements, and how packages bring everything together for deployment. We also explore the role of source control using Azure DevOps and the importance of building models before creating deployable packages. Watch this video to gain a comprehensive understanding of the key components in Visual Studio for finance and operations development.

Keywords: elements, models, packages, Visual Studio, finance and operations, application explorer, AOT, metadata, source files, base enumerations, tables, Finance Operations project, warehouse management model, deployable package, Lifecycle Services, runtime environments, wizards, designer window, user interface, source control, Azure DevOps, Application Explorer, create model, build models, development project, metadata development, Visual Studio tutorial.

Hashtags: #VisualStudio #FinanceAndOperations #ElementsModelsPackages #AzureDevOps #SoftwareDevelopment #DeveloperTools #ApplicationExplorer #Deployment #MetadataDevelopment #ModelManagement #SourceControl

Elements, models, and packages

Elements, models, and packages represent the structural hierarchy in Visual Studio for finance and operations. Elements either exist out of the box in the application explorer (AOT) in Visual Studio, or they can be created. Elements are metadata and source files, such as base enumerations and tables. A Finance Operations project is used to organize and manage elements within a model. Models contain zero or more elements. For example, the warehouse management model is a group of elements that make up the warehouse management solution.

All models belong to packages, which can then be packaged together to create a deployable package and then deployed by using Lifecycle Services. A deployable package contains one or multiple packages that are used for runtime environments. Wizards in Visual Studio are used to create models and projects, and the designer window is used to customize elements within projects and models.

Deployable packages are deployed to finance and operations environments. These packages contain models that, in many cases, represent the modules that are visible in the user interface, such as Accounts payable. The models contain the elements that represent every field, menu, and page that is found in the user interface. These elements are created and managed in Visual Studio. Therefore, source control using Azure DevOps is required for finance and operations development.

The following image shows the Application Explorer window in Visual Studio.