web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Custom Report Layout Export error - Invalid Namespace

(4) ShareShare
ReportReport
Posted on by 4,021
I added new Custom Word Layout for a built-in Report ID 1304 Sales Quote. When I export the Layout, it gives "invalid namespace" errors for many fields as shown below. I have not changed anything in the default report. Please advise how to fix it. Thank you.
 
Error message example:
The Word layout does not comply with the current report design (for example, fields are missing or the report ID is wrong).
The following errors were detected during the layout validation:
/NavWordReportXmlPart/Header/CustomerAddress1 has an invalid namespace xmlns:ns0='urn:microsoft-dynamics-nav/reports/Standard_Sales_Quote/1304/'.
/NavWordReportXmlPart/Header/CompanyAddress1 has an invalid namespace xmlns:ns0='urn:microsoft-dynamics-nav/reports/Standard_Sales_Quote/1304/'.
I have the same question (0)
  • Suggested answer
    YUN ZHU Profile Picture
    99,974 Super User 2026 Season 1 on at
    Hi, The Custom Report Layout feature has been deprecated.
    Please use the following features to export your layout.
    New pages for report layout administration (page 9660 “Report Layouts”)
    Dynamics 365 Business Central: Why are custom columns/fields added via Report Extension not found in standard layouts exported from Report Layouts page?
     
    Thanks.
    ZHU
  • Suggested answer
    OussamaSabbouh Profile Picture
    14,539 Super User 2026 Season 1 on at
    Hello ,
     
    This error happens because the Word layout’s XML namespaces no longer match the current dataset definition of Report 1304, even if you didn’t change anything manually; it typically occurs after BC updates, cross-environment copies, or when Word (especially Word Online) alters the custom XML parts. The practical fix is to recreate the custom layout from the built-in layout (Custom Report Layouts → New → Insert Built-in Layout), then export it immediately to confirm it’s clean, and only edit it afterward in desktop Word. In some cases, using Update Layout first is enough, but if namespaces are already corrupted, recreating the layout is the only reliable solution.
     
    Regards,
    Oussama Sabbouh

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,024 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,145 Super User 2026 Season 1

#3
Khushbu Rajvi. Profile Picture

Khushbu Rajvi. 705 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans
Liquid error: parsing "/blogs/post/?postid=%27nvOpzp;%20AND%201=1%20OR%20(%3C%27%22%3EiKO))," - Too many )'s.