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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Export a project thoug...
Microsoft Dynamics AX (Archived)

Export a project though command line

(0) ShareShare
ReportReport
Posted on by MDeeb 92

HI Everyone,

am using Devops in AX 2012 , to push everything from Developmen to UAT, to Produuction automicatically, it worked fine with models when exporting /importing models, however I want to move projects instead of models, I just still need to know how could I export a project through command line and not manually.

Thank you,

*This post is locked for comments

I have the same question (0)
  • Verified answer
    nmaenpaa Profile Picture
    nmaenpaa 101,162 Moderator on at

    I don't think that's possible. You should use models or modelstore for deployment.

    Please check this MS whitepaper: docs.microsoft.com/.../deploying-customizations-across-microsoft-dynamics-ax-2012-environments-white-paper

  • MDeeb Profile Picture
    MDeeb 92 on at

    Hi Nikolaos,

    Many thanks for your usual supportive answers, moving models takes more time and it always generate id conflicts, that's why am using projects instead specially that most of our customizations are minor, and already exists in USR model in USR layer. Moreover whenever I import a model, I have to do full compilation.

    Thank you,

  • Verified answer
    nmaenpaa Profile Picture
    nmaenpaa 101,162 Moderator on at

    What kind of ID conflicts are you talking about? Both xpo import and model import will cause ID differences between the source and target environments.

    You should do a full compilation after every code release (especially prod!) to be sure that the whole solution is still compileable. The only exception is modelstore release, which already contains compiled x++ code and CIL. So the fastest and most reliable deployment methodology is the modelstore deployment. And with modelstore delivery you will not have id conflicts - as long as the starting point is that both environments have same id values.

    Nothing stops you from delivering by xpos manually. But it can't be automated. And you should use model or modelstore deliveries, especially for production deployments.

  • MDeeb Profile Picture
    MDeeb 92 on at

    Thank you Nikolaos,

    so I will use export \import models, but what about if an element was moved in development environment to a different model  and then the model was imported to production, would this affect anything ?

    Regards,

  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,162 Moderator on at

    You need to export/import all changed models into your staging system, and do a modelstore delivery from staging to prod. This way you will always know that you won't face strange surprises during prod delivery.

  • MDeeb Profile Picture
    MDeeb 92 on at

    so can I export the model from Development to staging environment and perform full compile and then export the model store from staging and import it to production , does this also requires full compilation on production ? and I assume synchronization.

    Thanks a ot

  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,162 Moderator on at

    You don't need to run x++ compilation or CIL generation in prod if you do a modelstore delivery (since it was already done in staging, and you are copying the whole codebase). Synchronization is of course needed.

  • MDeeb Profile Picture
    MDeeb 92 on at

    thanks a lot Nikolaos, one more question data synchronization does not fail on any element in case the element model was changed right ?

  • Suggested answer
    nmaenpaa Profile Picture
    nmaenpaa 101,162 Moderator on at

    I don't understand the question.

    The sync can fail for example if you introduce a new unique index, but the existing data in the table violates the new index.

  • udaY-ch Profile Picture
    udaY-ch 5,133 on at

    Hi, Mdeeb

    As you import the modelstore into production, there is no possibility for element Id conflicts between your so called staging or test to production environment.

    /Uday.

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
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans