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 :
Small and medium business | Business Central, N...
Answered

How Can Multiple AL Code Programmers Work Together On The Same Project and Same Time?

(3) ShareShare
ReportReport
Posted on by 117
Hello, a question for those with experience:
I've been working alone on a (AL Code ) project for a long time in the system (Dynamics 365 Business Central) 
and I'd like an explanation of how to work with another programmer on the same project and same Time simultaneously without conflict. Is this possible?
And what method do I need to learn and successfully implement?
I have the same question (0)
  • Suggested answer
    Greg Kujawa Profile Picture
    787 on at
    Our company had similar challenges, since we performed AL development internally, and also contracted outside dev resources. It's pretty straightforward to leverage Azure DevOps to create a project that houses the AL code repository. Assuming it's a custom AL extension. Then different M365 users can be granted access. The users can create their own dev code branches, be assigned tasks as work items, etc. When things have been tested and pass, then those branches can be merged into main. 
  • Verified answer
    OussamaSabbouh Profile Picture
    10,875 Super User 2026 Season 1 on at
    Hello,
     
    How two developers can work on the same AL project safely
    The only correct way is to use Git (Azure DevOps or GitHub).
    Each developer works in their own branch, then merges with a pull request → no overwriting each other.
     
    What you need to learn
    Git basics: clone, branch, commit, push, pull, merge
    Branching strategy (feature branches)
    Optional but recommended: AL-Go for GitHub or Azure DevOps pipelines for automated builds
     
    Daily workflow
    Both developers clone the same repo
    Each creates their own branch for each task
    Work → commit → push
    Create Pull Request → review → merge
    CI pipeline builds the .app
     
    Regards,
    Oussama Sabbouh
  • Verified answer
    RockwithNav Profile Picture
    8,846 Super User 2026 Season 1 on at
    Use Git for check-ins.
    Make them work on there own solution and then eventually merge it once it all looks good.
    That's the easiest one.

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!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,155 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,043 Super User 2026 Season 1

#3
Dhiren Nagar Profile Picture

Dhiren Nagar 955 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans