![]() Use AxUtil to import and export application model data and work with the model store.ĪxUtil is a command-line utility that you can use to import and export. The AxUtil Command-Line Utility and Windows PowerShell Cmdlets Therefore, you no longer have to worry that you might run out of object IDs.Ĭhanging the length of object IDs from 16 bits to 32 bits exponentially increases the number of object IDs that are available. This change exponentially increases the number of object IDs. In AX 2012, the 16-bit object ID is upgraded to 32 bits. In earlier versions of Microsoft Dynamics AX, the number of object IDs that was available for application elements was limited, both in the range of IDs and by layer. In addition, you can use the tools that are available in SQL Server for backup and administration. Storing models in SQL Server increases quality, reliability, and performance. For example, you can use the SysModelElementLabel table to retrieve the string value for the label that is associated with a particular model element. These tables let you use model metadata in select statements in your X++ code. The new SysModel* system tables provide a view of the metadata that is associated with models. A new Model management submenu on the Tools menu contains many tools that you can use to work with models and the model store. ![]() You can generate a MorphX project that contains all the application objects in the model. When you add an element to version control, the element is added to the version-controlled model. ![]() The additional folder capabilities for version control have been renamed models, and the capabilities have been extended. The Microsoft Dynamics AX Application Object Tree (AOT) shows the model that a particular element belongs to and also the layer tags. (This method resembles the method that is used to change the current company.)Īny element that is created in the current layer can easily be moved to another model in the same layer. You can change the current model by clicking the name of the current model on the status bar. All development work, such as creating a new class, becomes part of the current model in the current layer. aod files that were used at run time.ĭevelopment is performed in the current model in a given layer. Model files can be signed, and the signature is verified when the model files are installed. Models in the model store can be exported to model files and imported from model files. aod file from earlier versions, but the names and numbers are not limited. Models can be exported to a file artifact that is known as a model file. For example, VAR Model is the model that is generated for the VAR layer.Įach element in a layer must belong to only one model. One of the models is generated by the system. aod files by using the Tools menu.Ī model is a set of model elements in a specific layer.Įach layer consists of one or more models. ![]() Use the model store to work with business data or customer data. AX 2012 introduces the model store, which is based on Microsoft SQL Server. Each layer of the application had a corresponding. In earlier versions, application model data for Microsoft Dynamics AX was stored in a proprietary database that was named the Application Object Database (AOD). Tools Used With Models and the Model Store Type Hierarchy Browser and Type Hierarchy Context The following tools have been added or enhanced in AX 2012: The AxUtil Command Line Utility and PowerShell Cmdlets The following MorphX development features have been added or changed in AX 2012: This topic lists the new and enhanced features and tools for the Microsoft MorphX development environment that is available in Microsoft Dynamics AX 2012. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.Īpplies To: Microsoft Dynamics AX 2012 R3 For the latest documentation, see Microsoft Dynamics 365 product documentation. This content is archived and is not being updated.
0 Comments
Leave a Reply. |