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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

How to Map a new TFVC branch and push project content ?

(1) ShareShare
ReportReport
Posted on by 508
I created a branch called developer-1 from the main branch in TFVC Azure DevOps I have set up the following mappings for developer-1 branch

Metadata: C:\AOSService\PackagesLocalDirectory
Projects: C:\Users\developerUserName\source\repos
 
The Azure DevOps pipeline is configured to run on the main branch I should pushing code to the developer-1 branch and then merging it into the main branch as I am new in d365 X++ it is a bit confusing for me

I have the following questions so far
-Do I need to map the main branch in the same way as the developer-1 branch?
-How do I push my changes (such as classes, forms, tables, and reports) from my local machine to the developer-1 branch, including both the metadata and project files? For example, if I am working on a solution in Visual Studio that contains a project with classes, forms, and tables, how should I push these changes?

thanks
I have the same question (0)
  • Suggested answer
    Martin Dráb Profile Picture
    239,036 Most Valuable Professional on at
    If developers develop just against developer-1, it's the only branch you need to have mapped to PackagesLocalDirectory. If all developers also merge code to Main, they'll need a mapping to Main too, but it can be in any folder (e.g. c:\MyRepo).
     
    If you want to develop in multiple branches and switch between them, it's more complicated, but feasible.
     
    To push commit changes to TFVC, add your solution to source control, which also adds all the objects inside, and then check-in the changes.
  • D365FO Junior-Dev Profile Picture
    508 on at
    Hi @Martin Dráb thank you for your reply,
     
    I have mapped only the developer-1 branch as show below after pushing the code I tried to merge the branch into main but I faced an error indicating that I need to map the main branch as well

    developer-1: 
    Metadata: C:\AOSService\PackagesLocalDirectory
    Projects: C:\Users\developerUserName\source\repos
     
  • Martin Dráb Profile Picture
    239,036 Most Valuable Professional on at
    I already covered this topic in my previous reply: If all developers also merge code to Main, they'll need a mapping to Main too, but it can be in any folder (e.g. c:\MyRepo).
  • Verified answer
    Anthony Blake Profile Picture
    3,092 Super User 2026 Season 1 on at
     
    My usual approach is to have another folder somewhere, e.g. K drive on a CHE, which is mapped to the root directory of you TFVC source repo, in its own workspace. 
     
    Something like:
     
    K:\ProjectRoot
    -Dev
    --Projects
    --Metadata
    -Main
    --Projects
    --Metadata
     
    Then from visual studio, open this workspace in source explorer, and you can right click the dev branch and merge to main. You can merge changsets for specific changes (be careful with this), or latest for everything.
     
    Anthony
     

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 658

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 468 Super User 2026 Season 1

#3
Syed Haris Shah Profile Picture

Syed Haris Shah 333 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans