- Feature
- Restrict global symbol resolution to a minor version
- Availability
- Generally available (October 2026)
- Industry focus
- Aerospace and defence supply chain
Aerospace and defence suppliers work under configuration control. Every change to a product, process or system has to be deliberate, documented and traceable. That culture extends to the software that runs the business. Business Central 29.0 gives development teams a tool that fits it: predictable control over which version of dependencies their extensions build against.
The industry challenge
A precision machining or component supplier to aerospace primes might extend Business Central for:
- First article inspection records
- Certificate of conformity output
- Material traceability from mill certificate to finished part
- Customer-specific quality clauses on purchase and sales orders
These extensions depend on the Business Central base application and often on other apps. When developers build them, the AL tooling downloads symbols for those dependencies. With global symbol sources, the newest available versions could be picked up, including a newer minor release than the one the team intended to test against.
That creates a quiet but real risk. A build that worked last week might behave differently this week, not because anyone changed the code, but because a dependency moved. In a controlled environment, "we're not sure which version we built against" is not an acceptable answer.
What Microsoft delivered in Business Central 29.0
According to Microsoft, developers can now set global symbol downloads to stay within the major and minor version stated in app.json, while still taking the newest available patch for all dependencies.
Microsoft describes the business value as more predictable symbol restoration. It stops dependencies moving to a newer minor release unexpectedly. Teams can reproduce builds and test extensions against the intended minor version, while still getting compatible patch updates.
Where the value shows up
| Business area | Impact for an aerospace and defence supplier |
|---|---|
| Configuration control | Builds target a known Business Central minor version |
| Reproducibility | The same code produces the same build, run after run |
| Quality assurance | Test results apply to the version that will actually ship |
| Security and stability | Compatible patches still flow in |
| Audit readiness | Clear evidence of which platform version an extension was built for |
The balance is the point. Locking everything would mean missing fixes. Floating freely would mean unpredictable builds. Pinning to a minor version while accepting patches gives controlled stability.
A worked scenario
Consider a supplier of machined titanium brackets to aircraft manufacturers (an illustrative example). Its quality extension generates certificates of conformity and must be validated against each Business Central version before use.
The quality manager's change procedure requires every extension release to be tested against the minor version that production will run. Before 29.0, a developer rebuilt the extension a few days after testing and unknowingly picked up symbols from a newer minor version. The quality team had to repeat part of the validation.
With Business Central 29.0, the team sets symbol resolution to stay within the minor version in app.json. Rebuilds pick up the latest patches but stay on the intended minor version. The validated build and the released build match, and the change record says so.
Adoption considerations
- Align app.json with your release plan. Make sure the declared version matches the platform version you intend to support.
- Move minor versions deliberately. Treat a change of minor version as a planned change with its own testing.
- Keep patch updates flowing. Patches carry fixes, so don't block them without a reason.
- Document the setting. Record it in your development standards and change procedures.
- Use it in CI pipelines too. Predictable symbols matter most in automated builds.
The bottom line
In aerospace and defence, predictability is a requirement, not a preference. Minor-version symbol pinning in Business Central 29.0 brings configuration-control discipline to extension builds. It makes them reproducible and testable without cutting off important patches. For suppliers who must evidence every change, it's a welcome addition.
If your organization runs validated or controlled extensions on Business Central, it's worth reviewing your build and release process with an experienced adviser.
Source: Microsoft roadmap 573357