- Feature
- Manage report layout lifecycles
- Availability
- Generally available (October 2026)
- Industry focus
- Chemical and specialty materials manufacturing
Chemical manufacturers send documents that carry real responsibility: certificates of analysis, dangerous goods declarations, delivery notes with hazard information and invoices with regulatory statements. Using the wrong or outdated document layout isn't just untidy. It can be a compliance failure. Business Central 29.0 gives administrators tighter control over which layouts people can use.
The industry challenge
Over time, a Business Central environment collects many report layouts:
- Standard layouts shipped by Microsoft
- Layouts from AppSource apps, such as a quality or labelling app
- Per-tenant extension layouts built by partners
- User-created copies made for one-off needs
In a regulated chemicals business, only some of these are approved for external use. A certificate of analysis layout may have been validated by the quality team, while an older copy without the latest regulatory text still sits in the list. If a user picks the wrong one, a non-compliant document can reach a customer.
Until now, administrators had limited control over layouts that came from Microsoft or from apps.
What Microsoft delivered in Business Central 29.0
According to Microsoft, administrators can now set a status on all types of layouts. That includes layouts shipped with Business Central, per-tenant extensions and AppSource apps. The status controls which layouts are available to end users.
In practice, this gives administrators a lifecycle to manage. They can make approved layouts available, keep draft layouts out of users' hands, and retire old layouts without deleting them.
Where the value shows up
| Business area | Impact for a chemical manufacturer |
|---|---|
| Regulatory compliance | Only approved layouts can be used for customer documents |
| Quality control | Draft and outdated layouts stay out of circulation |
| Change management | New layouts can be prepared and approved before release |
| User experience | Shorter, cleaner lists of layouts to choose from |
| Audit | Clear evidence of which layouts were approved for use |
This brings document layouts into the same change-control discipline that chemical companies already apply to formulas, specifications and procedures.
A worked scenario
Consider a manufacturer of industrial coatings that ships to customers across Europe (an illustrative example). Its certificate of analysis must include updated regulatory statements from next quarter.
The quality team works with the partner to prepare a new layout, but it must be reviewed before use. With Business Central 29.0, the administrator keeps the new layout unavailable while it's in review. Once approved, they make it available and set the old version so users can no longer select it. An extra layout from an AppSource labelling app, which the business doesn't use for certificates, is also hidden. Shipping staff now see only the approved layout, and the risk of sending an outdated certificate falls sharply.
Adoption considerations
- Inventory your layouts. List every layout in use and decide which should be available.
- Define a lifecycle. Agree what each status means, such as draft, approved and retired, and who can change it.
- Link to document control. Treat customer-facing layouts as controlled documents in your quality system.
- Communicate changes. Tell users when layouts are added or retired.
- Review after updates. New Business Central versions and app updates may add layouts. Check their status after each update.
The bottom line
For chemical manufacturers, documents are part of compliance, not an afterthought. Layout lifecycle control in Business Central 29.0 makes sure only approved formats reach customers, regardless of where a layout came from. It's a governance feature that brings report layouts under the same control as the products they describe.
If document compliance matters in your business, it's worth reviewing your report layouts and approval process with an experienced Business Central adviser.
Source: Microsoft roadmap 573320