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)

VSTS Model to Source Control 101

(1) ShareShare
ReportReport
Posted on by 3,542

HI. I'm still very new to VSTS.

Myself and a fellow developer (my senior) are working on a model XYZ. It is one of the main products of my company, thus we add new functionalities on a daily basis.

The main XYZ is on a server that my senior works on. I have a copy of the server on my computer.

We want to use VSTS so that I get the work he did and visa versa and in general that our separate versions stay up to date with each other. I understand that is one of the main points of VSTS.

I have numerous tabs open at the moment regarding the above mentioned subject, but I get lost as the help pages are quite extensive.

I would really appreciate a 101 on the correct mapping/setup to use so that our versions can stay up to date.

The current mapping on both my side and my senior is:

Source control $/XYZ/XYZ maps to local C:\AOSService\PackagesLocalDirectory\XYZ\XYZ

Source control $/XYZ/Projects maps to local C:\AOSService\PackagesLocalDirectory\XYZ\Projects

It works fairly well... But I have a hunch that something is not right - there are bugs. For example in some cases when I get the latest version of an element and try to build it, I get an error: (Paraphrase) "The element could not be found".

I read somewhere that the descriptor and metadata also needs to be mapped....

In any case the current mapping is not relevant - we'll change it to the "correct" mapping (whatever it is).

Thanks in advance

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    István Orosz Profile Picture
    2,137 on at

    It seems, not all objects are on the latest version, maybe you should try a full sync.

    Kind regards

    István

  • Pete Alberts Profile Picture
    3,542 on at

    Hi Istavan, thanks for the reply.

    Please read the whole post. :) If I may try to ask the question differently: Is it acceptable to upload a whole module to source control? Meaning the entire model folder of XYZ in PackagesLocalDirectory

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

    You can have anything you want in the source control.

    But these are the ones that you really need:

    - C:\AOSService\PackagesLocalDirectory\YourPackage\YourModel -> entire folder

    - C:\AOSService\PackagesLocalDirectory\YourPackage\Descriptor -> the descriptor for your model (must be added manually to source control)

    Most likely your error happens because you get only the latest version of one element, instead of getting latest of the whole project. It seems that the new version of the element is referencing another element which you don't have.

    Another possible explanation is that the other developer didn't add the referenced element to source control.

    So either you didn't get latest of everything from the source control, or someone didn't add all their new objects there.

  • Pete Alberts Profile Picture
    3,542 on at

    Thanks. Exactly the answer I was looking for :)

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