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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

Need one last bit of advice for migrating model content when using TFS...

(0) ShareShare
ReportReport
Posted on by 2,007

Thanks to the advice of this forum, we managed to successfully migrate our code from the system generated CUS model to a new model we created ourselves. We just have one last problem that I have an idea how to solve, but I was wondering if you guys had a better way to solve it.

Because of circumstances beyond our control, we created the branch we are currently working in because the previous branch was constantly being delayed. However, because of an issue with the previous branch build out, our moving the model was accelerated and happened in our new branch instead of the previous branch. That previous branch has just gone live and the changes are still part of the CUS system generated model. If I attempt to sync these changes to our new branch, I am assuming nothing will happen, since all of the new changes are in our custom model and not in the system generated CUS model.

I figure to resolve this issue, I just need to go through the check in history of the previous branch and figure out which objects got modified and import them into my new branch, since those objects have likely been moved to the custom model in the new branch or the objects are completely new and have to be migrated. However, I was wondering if there was an easier way to do this. I thought about re-syncing to the system generated CUS model and create a project to migrate all of the elements to our new custom model, but we have already checked in changes to the new model and I am not certain that doing that is the best of ideas.

If you guys could give me some advice on this one, I'd really appreciate it.

Brandt

*This post is locked for comments

I have the same question (0)
  • Verified answer
    Martin Dráb Profile Picture
    237,948 Most Valuable Professional on at

    Rather then importing objects to AX, it may be easier to replace objects at file-level. You will take modified objects from CUS folder of the other branch, put them to your model folder and synchronize your AX boxes with TFS. Of course, check if some files don't have conflicts - if so, you'll have to merge conflicting changes.

  • Brandt Fundak Profile Picture
    2,007 on at

    Martin,

    Thanks for helping me get out of my tunnel vision. This idea makes the most sense and takes AX out of the equation. Thanks for your advice.

    Brandt

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…

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