AX Diary | D365 F&O

How to: Export and Import a Model [AX 2012] Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012 A model is a set of elements in a given layer. Each layer consists of one or more models. Models can be exported to files that have the .axmodel extension. These files are called model files. Model files are deployment artifacts that can be imported into a model store. A model is permanently associated with the layer that is created in. If you need to move one of your models from one layer to another, you must create a project from the model in the AOT, export the project as an xpo file, create a target model in the desired layer, delete the original model to avoid having to resolve layer conflicts, and import the xpo file to the target model. If you are moving elements between models in the same layer, you can use the Move to model command in the AOT. You can use either Windows PowerShell cmdlets or the ...

X++ Code to Export AOT Object / automatic backup of xpo's. we need to take daily backup of our development (interms of xpo) , but we all always forget becuase of our hectic work schedules. So use the following job and build batch application to take backup of developement in terms of xpo . We can take aod also but the size will be more and needs to stop AOS everytime . Following job illustrates how to export/backup all AOT Classes object. void GJ_ExportTreeNodeExample() { TreeNode treeNode; FileIoPermission perm; #define.ExportFile(@"c:\AOTclasses.xpo") #define.ExportMode("w") ; perm = new FileIoPermission(#ExportFile, #ExportMode); if (perm == null) { return; } perm.assert(); treeNode = TreeNode::findNode(@"\Classes"); if (treeNode != null) { // BP deviation documented. treeNode.treeNodeExport(#ExportFile); } CodeAccessPermission::revertAssert(); } Enjoy !!!!!!!!

“Connection with the Application Object Server could not be established” Scenario: Installing  Dynamics AX  2009/2012 in two different domains or two different networks. AOS  server in one domain (192.168.1.xxx network) and users and AX Client PC/ terminal servers in other domain (10.5.1.xxx network). When a AX client from a laptop attempts to connect to AOS you receive the following message or error “Connection with the Application Object Server could not be established”. Solution: It is network problem and you can solve it. Open  host file  (c:\windows\system32\drivers\etc\hosts) on the AX Client PC or  Terminal Server . Add  IP address  of AOS server and AOS server name 192.168.1.25     AOSServer in host file then Run the command  nbtstat-R  and start Dynamics AX Client.

SysOperation framework part 1: In Dynamics 2012, the runbase and RunbaseBatch has been replaced sysoperation framework. The main difference between the old and new framework is as following, Runbase and RunbaseBatch Sysoperation framework No controller class. Controller class to perform operation such as which UI to show. No contract class. Use of marco Contract class to store the data which need to display on the UI No UI class Separate UI class to handle the event and operation related to UI No Service class Service class to perform the business operation base on the input. In sysoperation framework we have three main classes which are as following Controller Class: The purpose of controller class is to perform the following operation Determine which UI should be used. Determine whether the operation can be perform in Batch. Determine the caption of the dialog Contract Class: The Contract class is use to save user input and gives it to service...