A Microsoft reference architecture guides the design of internal support with Copilot Studio. Permissions, escalation, and testing shape what is worth automating.
Business Central 29 combines controls over selectable layouts with APIs for querying the report inbox, retrieving files and updating their read status.
Documentation checked against Microsoft Learn on October 27, 2026. The BC29 release notes classify layout lifecycle control as generally available; the API references apply to 2026 release wave 2 and later. No functional tests were performed. The registered video could not be retrieved and is not used as evidence of a demonstration.
Availability in the release and in individual environments
Microsoft lists report layout lifecycle control as generally available in Business Central 29.0, the version that starts 2026 release wave 2. The inbox references also document API access from this wave.
Release availability does not confirm that every customer is already using it. Microsoft says administrators of existing online customers can schedule the upgrade within the update period ending in February 2027.
What a layout's status controls
The management guide allows administrators to change the status of one or several layouts from Report Layouts. For an extension-provided layout, Business Central saves the status change as an override and preserves the original layout.
The status reference distinguishes the following situations. Pending Approval indicates that review is outstanding; its name does not establish that an automated approval workflow exists.
Status
Documented effect
Draft
Being prepared; unavailable for selection.
Pending Approval
Ready for review; unavailable for selection.
Approved
Available for selection.
Retired
No longer available for selection.
What the inbox APIs support
The official references separate company information, inbox entries and file content. This distinction helps establish which parts of an integration are documented.
Retrieve the file name, output type, size and document content for an entry.
The inbox has a specific scope
The user documentation describes the inbox as a list of scheduled reports generated by the user. It does not include previous reports produced through the Print action or saved as files from the Reports menu.
These API references do not document operations for generating reports, emailing them or deleting them. Accessing an entry and retrieving its file therefore does not establish a complete production and distribution workflow.
Fictional example: two versions of an invoice
A fictional company maintains an older invoice layout while preparing a new presentation. As a proposed workflow from Nexo, it could organize the change as follows:
Prepare and review the new version while it remains a draft.
After review, approve it and check the default selection for each company before retiring the previous version. Microsoft explains that configuration in its layout selection guide.
In a separate process, query the inbox to locate a scheduled report, retrieve its file and update the read status after checking that processing succeeded.
Interpretation and integration limits
Nexo's editorial interpretation is that statuses help distinguish layouts ready for use from those still under review or already retired. The example above is not an observed execution. Nor does it demonstrate that marking an entry as read confirms delivery to a recipient.
The default layout selection is configured per company. It should be reviewed during a replacement, without assuming that a status change alone resolves every existing selection.
For a specific integration, API Overview exposes published APIs and their addresses in the current environment; the page neither configures access nor grants permissions. Online APIs are enabled by default, whereas on-premises installations require configuration. Authentication, effective permissions, file retrieval and extension compatibility should be checked in the target environment before deployment.
Created with AI assistance and reviewed by Nexo Community. Practical proposals and editorial interpretation are distinguished from documented facts.
Microsoft lists three enhancements in public preview: multiple excise duties per item, withholding on employee transactions and vendor-specific self-billing number series. Their application depends on the process and configuration.