Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics AX (Archived)

What is best practice for multiple model import?

(0) ShareShare
ReportReport
Posted on by 500

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

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

    Thanks Martin, Vilmos - much appreciated.

  • Martin Dráb Profile Picture
    Martin Dráb 230,445 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.

  • 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

  • _MGP Profile Picture
    _MGP 500 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?

  • 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.

  • Verified answer
    Martin Dráb Profile Picture
    Martin Dráb 230,445 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.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Verified Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,391 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,445 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans