Scribd
Upload
29 views

Using Visual Studio for X++ Development

Uploaded by

Moeez Buttar
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
29 views

Using Visual Studio for X++ Development

Uploaded by

Moeez Buttar
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Using Visual Studio For

X++ Development

Created By:
Moeez Nawaz
D365 F&O Technical
Consultant
Dynamics 365 SDK
The Dynamics 365 SDK (Software Development Kit) is a collection of libraries, tools, and documentation
designed to help developers interact with Microsoft Dynamics 365 applications. The SDK provides APIs,
sample code, and tools to help you build custom applications or integrate Dynamics 365 with other
systems.
Model Management
 A model in Dynamics 365 for Finance and Operations is a collection of
artifacts (objects) that define the business logic and user interface for a given
solution. Models allow developers to group related customizations and keep
them separate from other parts of the application.
 Models in D365FO contain a wide variety of elements, such as:

• Tables: Define the structure of the data used in the system.


• Classes: Contain business logic written in X++ (the proprietary language
used in Dynamics 365 FO).
• Forms: User interface components.
• Reports: Structured reports based on the underlying data.
• Queries: Define views on the data, used in reports, forms, or processing logic.
• Menu items: Provide links to various parts of the application.
• Data Entities: Enable data import/export and integration scenarios
 Types of Models
 In Dynamics 365 FO, models are categorized as follows:
 System Models: These are pre-defined models that come with the system.
Examples include the "Application Suite" or "System Administration"
models.
 Custom Models: These are user-defined models used for custom
development. Developers create these models to encapsulate custom
business logic, user interfaces, integrations, or extensions.
 Shared Models: These models are used for creating reusable components
that can be shared across multiple projects.
 Third-Party Models: These models come from external vendors and are
often used for specific business functionality or integrations.
 Model Layers:
 CUS: Customization layer, used for customer-specific developments.
 USR: User layer, for user customizations.
 SYP: System-wide platform (standard) functionality.
 LCS: Used for managing and maintaining the models in the lifecycle
services.
 Creating and Managing Models
 You create and manage models
through the Application Object
Tree (AOT) or Visual Studio.
 Steps to Create a Model:
 Open Visual Studio: Open Visual
Studio
connected to your Dynamics 365 for
Finance and Operations instance.
 Create a New Model:
 Go to File > New > Project.
 Select Dynamics 365 > Finance
and Operations.
 Choose the Model template.
 Name your model and choose the
Layer
(e.g., CUS for custom development).
Best Practices for Using Models in
D365FO
 Separation of Concerns: Use models to separate different
functionalities or business areas in your code. For example, put HR-
related customizations in a different model than those for finance.
 Reuse and Extensibility: Place reusable components (like classes or
data entities) in shared models to enable other projects or models to
reference them.
 Version Control: Models are often used with source control (like Git) to
manage the changes in a structured way.
 Environment Management: Models can be deployed to different
environments (Development, Test, UAT, Production) via Lifecycle
Services (LCS).
Create the Deployable Package

To create a deployable package, follow these steps:


1.Open the AOT (Application Object Tree):
•In Visual Studio, go to the Dynamics 365 menu.
•Select Build > Create Deployable Package.
2.Select the Model or Project:
•In the Create Deployable Package dialog, select the model or project for which you want to create the package.
•You can select either:
•All models: For creating a package that contains multiple models.
•Specific model: For creating a package for one particular model.
3.Configure the Package:
•Choose the Package Type (typically "Deployable Package" for most scenarios).
•Specify the Output directory where you want to save the generated deployable package.
•Optionally, you can also set a Version number for the package if you're deploying a new version.
4.Build the Deployable Package:
•Click Create to start the build process.
•Visual Studio will generate a ZIP file containing the model's metadata, resources, and other necessary components.
5.Verify the Package:
•Once the package is created, navigate to the output directory you specified.
•You should see a .zip file containing the deployable package.
.

You might also like