Microsoft Dynamics AX (Archived)

ID Conflict during the model store import

(0) Share

Report

Posted on by Community Member

Hi,

I'm using Import-AXModelStore and I receive this error:

ID conflicts were detected and the import operation is aborted.

Question 1 : How can I know which objects are in conflicts ?

I know that axutil importstore with the parameter /conflict push will create a model with my conflict objects, but I was wondering if there was an easier way.

Question 2: is it me or I need to create a temporary schema if I want to import a model store using axutil ?

If I use this command line: axutil importstore /file:C:\AxModelStore\test.axmodelstore /conflict:push

I receive ERROR: The APPLY command line switch is required to run this program.

Can I apply the model store directly to the default schema ? How ?

Question 3 : Does it exist the equivalent of /conflict push with Import-AXModelStore ?

Import-AXModelStore comes with the parameter -IdConflict <String>

Can anyone explain me how to use this parameter ?

Thank you very much

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

Denis Macchinetti 16,444 on at

Like (2)

Report

Hi Matt

Usually I prefer to use the powershell commands.

So, about the first question, if you use Import-AXModelStore with the parameter /verbose and a conflict occurs, you will be able to see the objects with conflicts.

Also, if you raise the Import-AXModelStore command with the parameter -IdConflict Overwrite, you will be able to overwrite the objects with conflicts.

Take care in using this option.

Finally, if you want to reduce the downtime of the target env, you can import the Modelstore in a temporary schema and at the end apply it.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Denis.

You answered my first question, the verbose parameter tells me the conflicts.

Regarding my second and third question, is it possible to create a model with conflict objects using Import-AXModelStore

Thank you

Was this reply helpful? Yes No
Suggested answer

Denis Macchinetti 16,444 on at

Like (2)

Report

Hi Matt

To be honest, with Modelstore I never use the -IdConflict parameter just to avoid issue the IDs

However, with Modelstore you have two options :

1- Don't specify "-IDConflict" that is equivalent to "Reject" parameter of the Install-AXModel command

2- Specify "-IDConflict Overwrite" that is equivalent to "Overwrite" parameter of the Install-AXModel command

The Push option isn't possible with the Modelstore because :

1- The Modelstore is an "image" of the Source environment

2- The Modelstore contain the DLL libraries

3- The Modelstore is used to preserve the Objects IDs across the Environments

Was this reply helpful? Yes No
Suggested answer

Umesh Pandit 9,315 User Group Leader on at

Like (0)

Report

To import the Modelstore in a temporary schema and at the end apply follow steps:

Steps:

1. Open SSMS (SQL Server Management Studio) (Press the Windows Key + R, Run will open Type SSMS and enter)

2. Connect to the SQL Server instance where AX database resides

3. Expand to Databases > MicrosoftDynamicsAX_model > Security > Schemas

4. Right click > New schema

5. Type in the temporary schema name (TempoSchema) and select the schema owner and click "OK"

6. Initialize the temporary schema

For Initialize the temporary schema Use the command below:

Initialize-AXModelStore -AOSAccount "Domain\AccountName" -SchemaName <TempoSchema> -Server <ServerName> -Database <DatabaseName>)

Import model store to temporary schema

Syntax: Import-AXModelStore -File <filename> -TempoSchema

Example:

Import-AXModelStore -File “C:\AX\AX_ModelStores\AXModelStore.axmodelstore” -SchemaName “TempoSchema” –IdConflict overwrite -Config MicrosoftDynamicsAX -Details

Import-AXModelStore -Apply:TempoSchema -Config MicrosoftDynamicsAX -details

Was this reply helpful? Yes No