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 :
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / Best Practices for Imp...
Small and medium business | Business Central, N...
Answered

Best Practices for Implementing CI/CD Pipelines in Dynamics NAV 2018 (C/SIDE / C/AL)

(6) ShareShare
ReportReport
Posted on by CU17071040-0 24

Hi Dynamics Community,

Our client will continue on Microsoft Dynamics NAV 2018 (C/SIDE & C/AL) through end‑2026. We’re researching on implementing a CI/CD pipeline (Azure DevOps/GitHub Actions) and would appreciate your advice on:

  • Source Control: Object export formats, repo structure, branching for features/hotfixes

  • Build & Compile: Headless compilation tools (e.g., NavContainerHelper, Automation Toolkit) and error enforcement

  • Testing: Unit/integration test frameworks and result integration in pipelines

  • Packaging: Creating/versioning deployable artifacts (.fob/.navx), handling localization

  • Deployment: Automating app publish, schema sync, data upgrades with rollback strategies

  • Lessons Learned: Common pitfalls with schema changes, upgrade scripts, and YAML snippets or community extensions

  • Documentation: Links to any proper guidance or reference materials on CI/CD for NAV 2018

Thank you for any concise scripts, pipeline examples, or tooling recommendations.

Categories:
Microsoft Dynamics NAV
I have the same question (0)
  • Verified answer
    Sohail Ahmed Profile Picture
    Sohail Ahmed 11,169 Super User 2026 Season 1 on at

    Great question—setting up CI/CD for NAV 2018 (C/SIDE / C/AL) is possible, though less streamlined than AL-based extensions. Here's a concise guide based on community best practices:

     

     Source Control

     
    • Use Git with FOB or TXT format. Prefer TXT (ExportToNewSyntax=1) for readable diffs.
    • Organize repo by object type (e.g., Tables, Codeunits) with clear branching strategy (main, dev, feature/hotfix).
     

    Build & Compile

     
    • Use NavContainerHelper with Docker-based NAV 2018 images.
    • Automate compilation via PowerShell scripts: import TXT → compile → export FOB.
    • Enforce compile errors by stopping the pipeline if any objects fail.
     

    Testing

     
    • Use Test Toolkit objects delivered by Microsoft (if available).
    • Integrate tests using PowerShell and parse results into Azure DevOps or GitHub Actions.
     

    Packaging

     
    • Create versioned .fob packages after successful build/test steps.
    • Handle localization by separating language-specific objects or using translation files.
     

    Deployment

     
    • Automate via PowerShell: import .fob, run schema sync, and handle data upgrades.
    • Include pre-check scripts for schema conflicts and create backups for rollback.
     

    Lessons Learned

     
    • Avoid heavy schema changes in core tables.
    • Always test upgrade codeunits in a staging environment.
    • Common pitfalls: missing dependencies, locked objects, and version mismatch.
     

    Documentation

       

    Let me know if you'd like a sample YAML or PowerShell pipeline template.

     

    ✅ Mark this answer as verified if it helps you.

  • Suggested answer
    Ramesh Kumar Profile Picture
    Ramesh Kumar 7,547 Super User 2026 Season 1 on at
    Everyone has their one way of practice but here is below I suggest
     
     
    Source Control Git (branch-per-feature/hotfix)
    Build NavContainerHelper, import .fob & compile
    Tests Invoke-NAVCodeunit + parse logs
    Packaging Artifact pipelines: .fob or .navx
    Deployment PowerShell + container automation
     
     
     
    Thanks
    Ramesh
     
    If this was helpful, please check the "Does this answer your question?" box and mark it as verified.
     
     

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!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

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

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 1,926 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,158 Super User 2026 Season 1

#3
Khushbu Rajvi. Profile Picture

Khushbu Rajvi. 533 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans