Skip to main content

Export Import Model - Power Shell & Command line statements

I myself often require following commands and worth to have these at one place to get it more quickly. 

Export a Model File
Windows PowerShell
Export-AXModel -Model <name> -File <Filename.axmodel>
Example: daxture is a model name and it exist in C drive
Export-AXModel -Model daxture -File C:\daxture.axmodel

Export-AXModel -Server SERVERDB -Database DataBaseName –Model "Model Name" -File c:\temp\xxxxx.axmodel

AXUtil Command
axutil export /model:<modelname> /file:<filename> /verbose
Example: daxture is a model name and it exist in C drive
axutil export /model:"daxture" /file:"C:\daxture.axmodel" /verbose

Import a Model File
Windows PowerShell
Install-AXModel -File <Filename.axmodel> -Details
Example: daxture is a model name and it exist in C drive
Install-AXModel -File C:\daxture.axmodel -Details

Install-AXModel -Server SERVERDB -Database DatabaseName -File c:\temp\xxxxx.axmodel -DETAILS -Conflict Overwrite

In case of conflict we can use this command; Intall -AXModel -File <Filename.axmodel> -Details -Conflict Push

AXUtil Command
axutil import /file:<filename> /verbose
Example: file exist in C drive
axutil import /file:"C:\daxture.axmodel" /verbose


AxUtil commands
Creating a model in layer axutil create /model:"daxture" /Layer:CUS
Delete a model axutil delete /model:"daxture"
Delete a layer axutil delete /layer:ISV
Delete a layer from database and AXServer axutil delete /layer:ISV /db:<database> /s:<server>

Comments

Post a Comment

I will appreciate your comments !

Popular posts from this blog

The Dual Write implementation - Part 1 - Understand and Setup

What is Dual-write? Tightly couples – complete at one transaction level Near real time Bi-directional Master data and business documents – Customer records you are creating and modifying and at this document we are talking about sales orders or quotes and invoice. Master data could be reference data e.g. customer groups and tax information Why Dual-write and why not Data Integrator? Data Integrator is Manual or Scheduled One directional Now, Let's deep dive and understand what is required for Dual-write setup and from where to start. First thing first, check you have access to https://make.powerapps.com/ Choose right environment of CDS (CE) Make sure you have access to the environment too, click on gear icon and Admin Center  Look for required environment and Open it, you must have access as going forward you are going to configure dual write steps in the environment user the same user you are logged in now. Now, go back to power platform admin center and

D365FO: Entity cannot be deleted while dependent Entities for a processing group exist. Delete dependent Entities for a processing group and try again.

Scenario: There are times when you want to delete an entity from target entity list and when you do so, you face an error message which does not tell you where exactly the entity has been used.  "Entity cannot be deleted while dependent Entities for the processing group exist. Delete dependent Entities for a processing group and try again. " Solution: Browse the environment by appending this part  /?mi=SysTableBrowser&TableName=DMFDefinitionGroupEntity&cmp=USMF   at the end.  For example; if the environment URL is  https://daxture.sandbox.operations.dynamics.com then the complete URL will be https://daxture.sandbox.operations.dynamics.com/?mi=SysTableBrowser&TableName=DMFDefinitionGroupEntity&cmp=USMF Filter for Entity and it will give you the DefinitionGroup where the entity has been added or used in data management import/export projects. Get the DefinitionGroup name and search in the export/import projects under data management and either delete the whole

AX 2012 : Add/Remove Dynalink through X++

DynaLinks can be removed and added between datasources on form using this code; ClearDynaLinks() will remove all existing dynaLinks [these can be seen by right click on the click > Personalise > Query tab > under dataSource node AddDynalink() method has three parameters; 1. Source table field 2. Destination table 3. Destination table field The following code is implemented in the Click event of a button. void  clicked() {     SalesQuotationLine_ds.query().dataSourceNo( 1 ).clearDynalinks();     SalesQuotationLine_ds.query().dataSourceNo( 1 ).addDynalink( fieldNum (SalesQuotationLine, QuotationId),                                                          SAB_DocQuoteGroupRelation,                                                           fieldNum (SAB_DocQuoteGroupRelation,SalesQuotationId));            }