Project Export and Import

-

Project Export and Import


Today I want to show how you can export and import projects. It’s very easy and similar to what can be done in AX 2012.

Export

If you want to export a project of course first you need one – literally – in Solution Explorer. Right-click it and choose Export Project YourProjectName.
Export Project Dialog
In the Select Project Package File Name dialog you need to provide the path and name of the resulting project file. The file extension is .axpp. 

Import

Importing a project is super-simple, too. In Visual Studio, click on Dynamics AX > Import Project… and pick the axpp file you want to import (File name). Also you need to define the Project file location. There’s two choices in the Settings area. If you check Overwrite Elementsyou won’t get prompted about overwrites of AX metadata or project files. Open project inlet’s you decide if you want to use the Current solution, open the project in a New solutionor do not put it in any solution (None). In the Details area you can expand the project and see the elements included. They’re selected by default but you can unselect node-wise to avoid the import of elements. This is similar to AX 2012, too.
Import Project Dialog
It’s important to note that the project doesn’t only come with the objects included but also carries the information about the layer and the package it belongs to. Especially the package part is interesting because you might import a project that was given to you by someone else – belonging to a package your environment doesn’t know at all. Good news is Visual Studio handles this and creates the missing package automatically and with correct references and everything!

Comments

Post a Comment

Popular posts from this blog

D365FO - Data integration by OData

-
Image
There are many ways to integrate with D365F&O OData is one of them. This post show you how to do simple integration.  Simple architecture  of OData with 3rd party application There are 3 main steps: Create a table, data entity, and OData service endpoint  Register and prepare (OData client) application authentication in AAD and D365FO Create OData client application  Create a table, data entity, and OData service endpoint First, we create a sample 'MyCar' table. CarID, BrandName, SerieName and Color declared as string, Price as real, and PurchasedDate as date. Then create an index for CarID and set that index to be table's Primary Index.  Then create a data entity. After finished creating, note some data entities, tables, and security privileges are added into project. Now, re-check what we've just created. Table   https://yourboxmainurl/?mi=SysTableBrowser&TableName=MyCar&cmp=DEMF&limitednav=true&lng=en-us OData https://yourboxmainurl/d...
Read more

Create or Update Product attributes using X++ in D365 F&O

-
This code is to update or insert product attributes for a boolean value. Each item will have its own boolean value. We cannot update the existing boolean value for a new item. For the first time, we have to create the attribute value record id for the item and then you can update if you want to make changes to the value based on the record id.  Please change the code according to your requirement.     /// <summary>     ///  To create or update product attribute     /// </summary>     ///     public void createOrUpdateProductAttribute()     {         EcoResProduct                       product;         EcoResDistinctProductVariant        variant;         EcoResProductInstanceValue          ecoResProductInstanceValue;     ...
Read more

Layers concept in D365

-
Image
Layers : Layers are the traditional AX concept but in D365, there is a new process where we extend layers as shown below. Also when you create your model, you specify which layer the model is going to live in. However the importance of layer is quite minimal for instance, you are not required to provide a key for your model to live in that layer. Previously layers were a single stack of code that over-layered upon each other. This new process uses layers but they are located in independent stacks. This was only an architectural overview of Dynamics AX 365.
Read more