Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

Comprehensive guide to using GIT/source control for NAV 2016+ development

(0) ShareShare
ReportReport
Posted on by

I am already familiar with GIT and source control... but I am looking to understand how to use it for Navision development. Just simple version/change tracking would be enough for me at the moment... so I would like to understand how I can export objects automatically to save them in a local git repo.  (I'll worry about merging later).

Is there a good guide that shows every step of how to achieve this?

*This post is locked for comments

  • Jesper Kenborg Profile Picture
    10 on at
    RE: Comprehensive guide to using GIT/source control for NAV 2016+ development

    If you want to have a source control for NAV/BC that is let complex than GIT, then I can recommend you look at the source control solution from NAVToolbox. You can get up running in 5 minutes and there is not required any additional NAV/BC license or objects. Check it out on www.NAVToolbox.com

  • Suggested answer
    Stefano Demiliani Profile Picture
    37,166 Most Valuable Professional on at
    RE: Comprehensive guide to using GIT/source control for NAV 2016+ development

    Yes, individual files absolutely. So you can track changes for every objects.

  • Hannes Holst Profile Picture
    5,767 on at
    RE: Comprehensive guide to using GIT/source control for NAV 2016+ development

    Yes - definitly seperate files. Otherwise you would store always one big file even when you only change a caption.

    Not sure about GIT, I did once work with a self-build version control which triggered the VC-application per command line or it did support a directory scan (so that you don't have to import manually).

  • Community Member Profile Picture
    on at
    RE: Comprehensive guide to using GIT/source control for NAV 2016+ development

    Right - the "automate a process..." is what I am interested in. Is there a certain strategy to go by? For instance.. I see you can export with filters to say "codeunits 1-10" - do people do this and save groups of CUs into a single txt file?  I am wondering what the best practice is.  Should I do that or should I always save individual CUs into separate txt files?  Does it matter?

    I could see separate files as the way to go - just so that if I am reviewing a file's change history I know there aren't other things contained in the file I am looking at. Seems cleaner that way.

  • Suggested answer
    Stefano Demiliani Profile Picture
    37,166 Most Valuable Professional on at
    RE: Comprehensive guide to using GIT/source control for NAV 2016+ development

    You have GIT native support only with VSCODE and AL. For C/AL you can automate a process where you export all the NAV Objects as TXT with Export-NavApplicationObject Powershell cmdlet and then save them on a GIT repo for source control.

    [View:https://docs.microsoft.com/en-us/powershell/module/microsoft.dynamics.nav.ide/export-navapplicationobject]

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

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Congratulations to all our community participants!

Adis Hodzic – Community Spotlight

We are honored to recognize Adis Hodzic as our May 2025 Community…

Kudos to the April Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard > Microsoft Dynamics NAV (Archived)

Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans