web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / What is best practice ...
Microsoft Dynamics AX (Archived)

What is best practice for multiple model import?

(0) ShareShare
ReportReport
Posted on by _MGP 506

How do I manage the import process with multiple model files from different sources?

e.g. I have a Partner model file (CUS layer) and an End-User model file (USR layer).

Can I simply import each model file using Install-AXModel and then run the full compile and database synchronise?

Or should I repeat the Install-Compile-Synchronise process for each file?

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 237,693 Most Valuable Professional on at
    RE: What is best practice for multiple model import?

    You can do it at once. First prepare the modelstore to the state you want and then compile X++ and CIL and synchronize DB.

  • Verified answer
    Vilmos Kintera Profile Picture
    Vilmos Kintera 46,149 on at
    RE: What is best practice for multiple model import?

    If they do not change the same objects, importing them one by one,  then compiling/synchring and doing extra steps required (setup, configuration, etc.) as per their documentation from the Partner/ISV are enough just once.

    If same objects are modified on the same layer, conflict model is created. You need to merge the code and resolve the conflicts.

    If you import an object on a higher layer on a model, that will overlayer the previous object and again you need to merge them.

  • _MGP Profile Picture
    _MGP 506 on at
    RE: What is best practice for multiple model import?

    Thanks for the reply - I understand your comment on modelstore (also in context of the comment from Vilmos below).

    How does a conflict in the modelstore state show up? After importing a model file? Or when you start the Client? I have not seen evidence of conflicts so far.

    Also, I've been stopping the AOS before I do the model import and only start it when I need to do the CIL compile. Is this acceptable or is there a good reason to keep AOS running during import and X++ compile?

  • Suggested answer
    Vilmos Kintera Profile Picture
    Vilmos Kintera 46,149 on at
    RE: What is best practice for multiple model import?

    Conflicts are explained in the model import MSDN documentation, and in the How to resolve article:

    technet.microsoft.com/.../hh352314.aspx

    technet.microsoft.com/.../hh446521.aspx

  • Martin Dráb Profile Picture
    Martin Dráb 237,693 Most Valuable Professional on at
    RE: What is best practice for multiple model import?

    It depends on what conflicts you mean. I assumed you're installing compatible models, if not you'll have to look for overlayering and logical conflicts.

    AOS should be down when you're installing models. You would have to start it for X++ compilation if you used the native compiler running inside AX client.

  • _MGP Profile Picture
    _MGP 506 on at
    RE: What is best practice for multiple model import?

    Thanks Martin, Vilmos - much appreciated.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Priya_K Profile Picture

Priya_K 4

#2
Alexey Lekanov Profile Picture

Alexey Lekanov 3

#3
Scott_itD Profile Picture

Scott_itD 2 Community Manager

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans