Version 29 has retired the Custom Report Layouts page that NAV-era invoices, statements and remittances were often built on. A five-minute check to see if you are affected, what can go wrong, how to move your layouts safely, and what to look for on your first invoice run after the update.
Picture the first invoice run after your Business Central update. The invoices go out on time, but the logo has moved, the bank details have vanished from the footer and the terms and conditions are back to Microsoft's standard wording. Nobody changed anything. The layout your business had been using for years simply is not the one being used any more.
That is the risk in Business Central 2026 release wave 2 (version 29) for anyone whose documents were customised the old way. The Custom Report Layouts page, a feature carried over from Dynamics NAV, has been retired. The good news: it takes about five minutes to find out whether you are affected, and the fix is built into Business Central.
For most of its life, Business Central has had two places to keep a changed layout. The old one, Custom Report Layouts, dates from NAV and only ever handled Word and RDLC files. In 2022 (version 20) Microsoft introduced the Report Layouts page, which handles Word, Excel, RDLC and external layouts, lets you keep several versions of a layout and choose a default, and is where every new feature since has been built. From then on the old page was officially obsolete. Microsoft kept it working through version 28; in version 29 it has gone.
Systems most likely to be caught out are the ones that work perfectly. If you upgraded from NAV, or had your documents designed before 2022, your layouts were almost certainly created the old way, and because they never needed changing, nobody had a reason to move them.
| What you might see | Why it matters |
|---|---|
| Your logo, colours or fonts disappear from documents | Customers receive documents that do not look like they came from you. |
| Bank details, VAT number or company registration details missing or wrong | Payments go astray or are delayed, and invoices may not meet legal requirements. |
| Your terms and conditions revert to standard text | You lose the contractual wording your business relies on. |
| Extra fields you added (delivery instructions, project codes, customer references) vanish | Customers reject or query invoices, and payment slows down. |
| No one can edit the layout when something needs changing | A simple change, like new bank details, becomes an urgent job for your partner. |
Business Central has a built-in migration, available from version 27.2, so this is a check-and-convert job rather than a rebuild.
A word of caution: we have not been able to confirm whether the version 29 upgrade converts any remaining custom layouts automatically. Assume it does not. Converting them yourself beforehand is an hour's work; discovering the problem on the morning of your invoice run is not.
On the first working day after your update, before the main invoice run, print one of each customer-facing document and compare it with last month's. If anything looks different, stop the run and check Report Layout Selection first: in almost every case the report has fallen back to Microsoft's standard layout because it was still pointing at a custom one. Your exported files from step 1 mean the fix is quick.
OnAfterHasCustomLayout with OnSelectReportLayoutCode and OnFetchReportLayoutByCode. ReportGetCustomRdlc has been obsolete since version 20.Business Central online customers can choose their version 29 update date in the admin centre, up to the end of February 2027. Check yours today, move it away from month-end if needed, and book the layout conversion for a week or two before it. On-premises customers should build it into the upgrade plan and test it in the test environment first.
Once your layouts live on the Report Layouts page, you get more than survival. You can keep alternative layouts (a branded invoice and a plain one, say) and choose the default per report, retire old layouts by marking them obsolete so users stop picking them, build Excel layouts for analysis reports, and use version 29's new document features: themes, reusable headers and footers, and conditional visibility in the Word add-in. More on the release in Business Central version 29: what matters for a UK business.
We never changed a layout. Do we need to do anything? No. Standard layouts and layouts supplied by apps are not affected.
Will we lose our layouts? Not if you convert them first. Exporting them before you start means you always have a copy.
Can our finance team do this themselves? Usually, yes, if the layouts are simple and someone is comfortable testing documents carefully. If your layouts were built by a partner, contain code-driven fields, or there are many companies, it is worth having someone who has done it before.
Does this affect email bodies? If you use customised email body layouts for sending documents, check them in Report Layout Selection in the same way and convert any that are custom.
Credit where it is due: Yun Zhu, a Microsoft MVP, was first to spot that the page had gone in version 29. These are the best places to go deeper:
Open Report Layout Selection today. If any report uses a custom layout, export it, run Migrate to System Layouts, point the report at the new layout and test the real documents before your version 29 update. If none do, you have nothing to worry about.
Would you rather we checked for you? It is usually a short job, and we will tell you exactly how many layouts you have and what they cover. Book a 30-minute call.