How to resolve ID conflict with axmodelstore import

(0) Share

Report

Posted on by M.H.M.M. van den He...

750

Is there a whitepaper available which explaines how to resolve any ID conflict when importing an AXmodelStore from a different database. I'm receiving several ID-conflict because there where, in the past, several updates imported by XPO. Even have some ID conflicts with patched (ISP) ax base enums. Can anyone explain what steps to follow to resolve this.

Thanks,

*This post is locked for comments

I have the same question (0)

All responses (19)

Answers (0)

Anna 55 on at

Like (0)

Report

After the filename use the parameter /idconflict:overwrite

When running, AXUtil will display a warning "Continuing can lead to inconsistent data", choose Y

In case a conflict is related to a base enum or EDT, there should not be any problem with overriding the ID. In case ID conflict occurs on a table or a table field, there might be a data issue after.

Was this reply helpful? Yes No
Donna Marshall on at

Like (0)

Report

This white paper might help you: www.microsoft.com/.../details.aspx.

In addition, there is a lot of content on TechNet related to models and the model store: technet.microsoft.com/.../hh335181.aspx.

Was this reply helpful? Yes No
M.H.M.M. van den He... 750 on at

Like (0)

Report

I've read lot's of documentation, received the same info from microsoft, but none of them dealt with resolving ID-Conflicts. All were about preventing in stead of resolving.

I'm hoping to hear from someone in the field how has dealt with id-conflicts and hopefully resolved them satisfactory.

But thanks anyway for your help.

Was this reply helpful? Yes No
Mark Simmerman 1,325 on at

Like (0)

Report

I read your first post, understood it, and we are in the same boat. Microsoft documentation only addresses how not to get into an ID conflict, not how to resolve them; especially from multiple coding sources (different developers). If you solve it before we do, then please post your method here, and we will do the same. Most of the methods that we are testing are very time consuming and still leave room for error.

Kind Regards,

Mark Simmerman

Was this reply helpful? Yes No
Martin Dráb 237,948 Most Valuable Professional on at

Like (1)

Report

Hi Mark, either I don't understand your problem or you create an artificial one.

You shouldn't try to merge several model stores - simply install models from several sources and let AX to assign its installation-specific (= modelstore-specific) IDs. It was introduced in AX2012 exactly for this purpose.

If you change the whole model store, you're automatically getting into troubles, because your application suddenly use other IDs than your data. But you should almost never do that.

It's important to understand how IDs are assigned and what is the role of the Origin property. You can find the description here: Maintaining Installation-Specific Element IDs and Element Handles.

Was this reply helpful? Yes No
640579632b5c4e6780a... 4,730 on at

Like (1)

Report

delete all the existing models before you import the model store.

Was this reply helpful? Yes No
AXT 1,699 on at

Like (0)

Report

Martin, if i install model files as you describe i'll get the error:

Install-AXModel -File C:\tmp\m11 -Config MicrosoftDynamicsAX -Conflict overwrite

+ FullyQualifiedErrorId : The model file references an element that belongs to another model that does not exists in the model store. You can use the /createparents

No difference if i leave the conflict parameter away or or with push.

Best Regards,

Martin

Was this reply helpful? Yes No
Martin Dráb 237,948 Most Valuable Professional on at

Like (0)

Report

This is not really a conflict, this means that you use some object which is not in the target application and in your model neither.

Maybe you're importing multiple models and you just need to do it in right order. Otherwise you have to either remove the reference, include the referenced object in your model or, as mentioned in the error messega, use -CreateParents switch to create some dummy implementation of these objects (so code won't work, but at least you'll be able to import the model).

Was this reply helpful? Yes No
AXT 1,699 on at

Like (0)

Report

Thanks for your fast reply. Yes i'm importing multiple model (VAR, CUS). So does this means i have to import all models including Foundation, Foundation Labels, Foundation Updgrade, etc. My scenario is to copy prod db to dev and afterwards restoring the CUS/VAR Models on dev.

Was this reply helpful? Yes No
Martin Dráb 237,948 Most Valuable Professional on at

Like (0)

Report

Imagine that you've added a field to a table which is not in the target environment. AX can't just place the field into air, so you have to use one of options I mentioned. That's logical.

In your case, it means that your model depends on Foundation, therefore Foundation must be installed first.

But if you just make a copy of all code, don't bother about individual models - you can work with complete model store (Export-AXModelStore, Import-AXModelStore).

Was this reply helpful? Yes No