Symbols Issue while using CI/CD pipeline of ALGO GitHub BC SAAS.

(6) Share

Report

Posted on by Yash Mistry

113

Currently I'm using ALGO of GitHub for CI/CD of business central. I was able to successfully Automate that process.

But the issue now is like when I Extend Custom Table or Page Extension in my .al file I have to Download symbols. So, I also Given the Dependency in .APP file. But is there Any way that ALGO will Download Symbols on own from my Sandbox and Create .App with that.

Because of ALGO work using BCContainer I'm facing issue of Symbols. Is there any Solution about it?
thanks
Yash Mistry.

Categories:

Dynamics 365 Business Central

Microsoft Dynamics NAV

I have the same question (0)

All responses (2)

Answers (1)

Suggested answer

Sohail Ahmed 11,087 Super User 2025 Season 2 on at

Like (3)

Report

Symbols Issue while using CI/CD pipeline of ALGO GitHub BC SAAS.

adding more details

https://github.com/microsoft/AL/issues/5326

✅ Mark this answer as verified if it helps you.

Was this reply helpful? Yes No
Verified answer

Jeffrey Bulanadi 8,431 on at

Like (2)

Report
Symbols Issue while using CI/CD pipeline of ALGO GitHub BC SAAS.

Hi Yash,

Symbol resolution in AL-Go pipelines can be tricky, especially when extending custom tables or pages and relying on sandbox environments. The issue typically stems from how AL-Go uses BCContainerHelper to build against artifacts, which may not match your sandbox’s exact configuration or installed dependencies.

Here’s how to approach it:

First, make sure your .app file’s dependencies section includes the correct id, name, publisher, and version of the base app or any custom extensions you're referencing. If the referenced app isn’t available in the artifact cache or installApps list, symbol download will fail.

If your extension depends on another custom app (like Explore in your case), you’ll need to:

Include that app in the installApps array of your AL-Go settings.

Ensure the .app file is present in the repo or accessible via a shared artifact feed.

Use generateDependencyArtifact: true if you want AL-Go to build and cache dependencies automatically.

To pull symbols directly from your sandbox, you can:

Use the DownloadSymbols action with useCompilerFolder: true and point to your sandbox’s artifact version.

Authenticate using a valid token and ensure the environment is registered in your AL-Go settings.

If the app was manually installed in the sandbox and not part of the pipeline, AL-Go won’t be able to resolve it unless you explicitly include it in the build context.

As a fallback, consider exporting the .app from your sandbox using PowerShell and placing it in a dependencies folder in your repo. Then reference it in installApps.json.

Helpful References:
Symbol Download Error – GitHub Issue
Overview of AL-Go – Microsoft Learn
CI/CD Pipeline for BC – Jyotsna NAV Blog
Extending Standard APIs – Kauffmann Blog
BC Artifact Strategy – Dynamics 365 Lab

If you find this helpful, feel free to mark this as the suggested or verified answer.

Cheers
Jeffrey

Was this reply helpful? Yes No

Join the conversation

Community site session details

Symbols Issue while using CI/CD pipeline of ALGO GitHub BC SAAS.

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Abhilash Warrier – Community Spotlight

Congratulations to the September Top 10 Community Leaders!

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

Featured topics

Product updates

Community site session details

Symbols Issue while using CI/CD pipeline of ALGO GitHub BC SAAS.

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Abhilash Warrier – Community Spotlight

Congratulations to the September Top 10 Community Leaders!

Subscribe to this forum!

Select categories

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

Featured topics

Product updates