Every Business Central partner has fielded some version of the same client request: can our invoices look like they came from us, not from generic ERP output. The honest answer has usually involved a developer, a custom Word layout, and enough back-and-forth on colors and fonts that a genuinely simple branding request turns into a small project. Version 29 changes that calculus by borrowing a tool most people already know how to use.
The Underlying Idea: Themes Aren’t a BC Concept, They’re an Office Concept
Word, Excel, and PowerPoint have had a shared theming system for years coordinated colors, fonts, and effects, defined once and applied consistently across documents, with a Design tab anyone who’s used Office has already seen. Business Central’s new composable layout feature doesn’t reinvent that. It borrows it directly.
A new Subtype property now exists on Word layouts, with four values: Default, for every existing layout exactly as it’s always worked; Body, which marks a layout as one that can accept a separate theme and header/footer merged in at render time; Theme, for a layout that exists purely to define colors and fonts, saved as a .dotx template file; and HeaderFooter, for a layout defining just the header and footer portion. A Body layout references a ThemePart and a HeaderFooterPart, and Business Central merges all three together when the report actually renders.
What Building One Actually Looks Like
The practical workflow bypasses AL entirely for the branding part. Run an existing report with a Word layout Standard Sales Order Confirmation, for instance export it as a Word document, open it, and use the same Design tab a person would use to theme any Word document: switch the color scheme, change fonts, add a watermark, adjust the page color. Save the result as a Word Template file specifically, since saving it as a native Office theme file produces a .thmx file that Business Central doesn’t currently support the template format is what BC actually consumes.
From there, the new Manage Themes and Header-Footer Layouts page takes that saved template and registers it as a reusable theme inside Business Central. A newly created theme starts unapproved, and only approved themes can actually be assigned to a report a deliberate governance gate that keeps someone’s half-finished experiment from accidentally going live on a customer-facing document. Once approved, the theme and a matching header-footer layout attach to a Body-subtype layout through a new Composite Layout menu, and the report renders with the branding merged in automatically.
Why the Defaulting Structure Is the Actual Feature
Building one branded layout is useful. What makes this a platform capability rather than a one-off customization is where defaults can be set: globally, per company, per report, or per individual layout. An organization running multiple companies or brands under one Business Central tenant can apply one consistent look across everything by default, while still letting a specific report or a specific company override it where a genuinely different look is warranted.
That flexibility matters more than it sounds for BC partners managing multiple client tenants, or for any customer running multiple legal entities with distinct branding requirements. The old approach a custom Word layout maintained per report, sometimes per company, with no structural relationship between them meant every branding variation was its own maintenance burden. A shared theme applied at the right level collapses that into one asset that governs many outputs at once, with overrides available exactly where they’re actually needed.
What to Test Before Relying On It
A few constraints are worth confirming directly rather than assuming from the description. Themes and header-footer parts only apply to Word layouts RDLC layouts simply don’t have the option available, greyed out in the interface. And currently, no standard Business Central layout ships with the Body subtype already set; testing this feature means exporting an existing standard layout and re-importing it with the subtype explicitly changed, since Default-subtype layouts will throw an explicit error if you try to attach a theme or header-footer to them they have no body to merge one onto.
Finally
The most interesting thing about this feature isn’t the theming mechanism itself. It’s the decision to build it on top of a tool Word’s Design tab that a huge number of people already know how to use, rather than inventing a new Business Central-specific branding interface that someone would need to learn from scratch. A client’s own marketing or admin staff, not necessarily a developer, can plausibly produce a professional, on-brand document theme once the underlying Body-layout structure exists to hold it.
That’s a meaningfully lower bar than the old path of routing every branding request through custom AL and layout development, and it’s worth testing directly with a real client scenario before the next document-branding conversation comes up.
Leave a Reply