- Feature
- Evolve AL interfaces with default implementations
- Availability
- Generally available (October 2026)
- Industry focus
- Vertical software publishers (construction and project-based industries)
Software publishers that build construction and project-based solutions on Business Central face a constant tension. They need to add features for their market. But partners and customers have built their own extensions on top of the publisher's app. Any breaking change ripples outwards. Business Central 29.0 gives publishers a gentler way to move forward.
The industry challenge
A construction vertical app might expose AL interfaces that partners and customers implement, for example:
- A retention calculation interface, so each customer can apply its own contract rules
- A valuation or progress claim interface for different contract types
- A subcontractor payment interface for local tax schemes
Interfaces are powerful because they let others plug in their own logic. But until now, adding a new method to an interface was a breaking change. Every extension that implemented it had to be updated at the same time, or it would stop compiling.
For publishers, that meant either freezing interfaces, which slows innovation, or forcing coordinated upgrades across dozens of customers and partners, which is expensive and risky.
What Microsoft delivered in Business Central 29.0
According to Microsoft, Business Central 29.0 lets developers:
- Add default method bodies to AL interfaces, so existing implementations keep working when a new method is added
- Use a new RequiredPending transition attribute and analyzer rules to signal that a method will become mandatory in a future version
Microsoft explains the business value in two parts. Default methods give a compatible implementation, so dependent extensions don't have to change straight away. The transition attribute and AppSourceCop rules then provide a managed path for making a method required later, which gives dependent developers time to adopt the new contract.
Where the value shows up
| Business area | Impact for a vertical software publisher |
|---|---|
| Release speed | New capabilities can ship without waiting for every partner |
| Customer upgrades | Fewer broken extensions after an app update |
| Partner relationships | Partners get advance warning and time to adapt |
| Support cost | Fewer upgrade-related tickets |
| Product design | More confidence to use interfaces as extension points |
The strategic benefit is trust. Partners and customers invest in a vertical app partly because they believe it can evolve without breaking their work. Default implementations make that promise easier to keep.
A worked scenario
Consider a publisher whose construction app is used by 150 contractors through a network of partners (an illustrative example). Many partners have implemented its retention calculation interface for local contract forms.
The publisher wants to add a method that calculates retention release at practical completion. Before 29.0, adding that method would have broken every partner's implementation on the next update.
With Business Central 29.0, the publisher adds the method with a default implementation that applies the standard release rule. All partner extensions keep compiling and working. The publisher marks the method as RequiredPending and announces that it will become mandatory in a year. Partners schedule their changes into normal maintenance instead of rushing an emergency release.
Adoption considerations
- Choose sensible defaults. A default implementation should be safe and predictable for implementers who haven't updated yet.
- Communicate the timeline. Use RequiredPending alongside clear release notes so partners know when a method becomes mandatory.
- Use AppSourceCop rules. Let the analyzer flag pending changes early in partners' builds.
- Review existing interfaces. Identify interfaces that have been frozen because of upgrade risk.
- Test both paths. Check behaviour with the default implementation and with custom ones.
The bottom line
Vertical software publishers live or die by their ecosystem of partners and customers. Interface default implementations in Business Central 29.0 let them keep innovating without breaking the extensions their customers rely on. It's a developer feature with a clear commercial effect: faster releases, smoother upgrades and stronger partner relationships.
If you publish or depend on a Business Central vertical app, it's worth reviewing how its extension points are managed as part of your 29.0 planning.
Source: Microsoft roadmap 573352