Business Central report layout errors

Business Central renders documents (invoices, orders, statements) through a report layout — either a Word layout (mail-merge style) or an RDLC layout (a compiled report definition) selected per report, per customer, and per language. A layout error is almost always a mismatch between what the layout expects and what's actually configured or available, not a posting failure.

"No layout could be found for this report"

Symptom. Printing, previewing, or emailing a document fails because Business Central cannot find any layout to use for that report ID.

Cause. Every report needs at least one layout selected as available in Report Layout Selection (or the system default is being used but has been disabled), and the specific report, company, or customer combination has none assigned.

Fix. Open Report Layout Selection, find the report ID shown in the error, and either select an existing built-in layout or upload the custom one that should apply — checking company and customer-specific overrides, since a rule scoped to one customer can silently shadow the company-wide default.

Prevention. Whenever a new custom layout is uploaded to replace a built-in one, verify the selection in Report Layout Selection immediately rather than assuming the upload alone activates it.

"The report cannot be printed because a suitable report layout could not be found" after an extension update

Symptom. A layout that worked before an extension or base-application update starts failing to resolve, often right after a major release wave.

Cause. A Word or RDLC layout is tied to a specific report's data structure; when Microsoft or a partner extension changes that report's underlying dataset (adding, renaming, or removing a field the layout's XML schema references), the previously-working custom layout can become incompatible with the new report version.

Fix. Re-export the report's data schema from the (now-updated) report and re-map the custom layout's fields against the new schema — this is a manual re-authoring step, not something that fixes itself, since the old layout file's internal XML still points at the old field structure.

Prevention. Re-test every custom layout against a sandbox environment before each biannual major release lands in production, the same way AL extensions are tested for the release.

"An error occurred during the processing of the report" (RDLC rendering failure)

Symptom. An RDLC-based report fails partway through rendering rather than failing to find a layout at all — the error is generic and gives little detail about the actual cause.

Cause. RDLC rendering errors are typically a data or expression problem inside the layout itself: a calculation referencing a field that returns null in some rows, a data type mismatch in a custom expression, or a grouping/aggregate expression that fails on an edge-case value (zero, negative, or blank).

Fix. Reduce the report to a minimal dataset that still reproduces the failure (one document, one line) and isolate which field or expression breaks — RDLC's own error text rarely names the specific expression, so the fastest path is testing the layout against a known-simple record first, then a known-problematic one.

Prevention. Design custom RDLC expressions defensively (guard against null and zero before dividing, concatenating, or comparing) rather than assuming production data will always match the shape used during layout development.

Emailed documents fail even though printing and preview work

Symptom. A document prints and previews correctly but fails specifically when Business Central tries to send it by email.

Cause. Emailing a document depends on both the layout rendering correctly and the email account/SMTP or Microsoft 365 connector configuration being valid — a working layout with a broken email setup produces exactly this split symptom, and the error message can point at either half depending on which step actually failed.

Fix. Confirm the layout renders to PDF successfully on its own (via preview or print-to-PDF) before troubleshooting email — if preview works, the fault is in email setup and outgoing email, not the layout.

Prevention. Test a new or changed layout via preview first, then via email, as two separate checks — bundling them makes a layout bug and an email-configuration bug indistinguishable from the symptom alone.

Where to go next

Building and customising layouts in the first place is covered in document layouts and report design in Business Central; the email delivery half of the pipeline is email setup and outgoing email in Business Central.