Small and medium business | Business Central, N...

Cannot create the Configuration Package Excel file for "Prod. Order Line"

(6) Share

Report

Posted on by JC-30041252-0

Hi, there

I am trying to migrate Work Order entries from GP to BC Production Order. For the Production Order Header (table 5405), I am able to import data from GP successfully. But I am facing problems on "Prod. Order Line" (Table 5406). I created a testing Configuration Package to prove this, as shown below, to illustrate the problem.

(Issue 1): Right after I exported the Excel file, I then loaded it into Excel. Excel told me there were issues within the Excel file as shown below.

(Issue 2): I managed to extract the data XML file inside the Excel file, and I saw there are 2 <tableColumn> as shown below with the same field "uniqueName" of "Status" inside the table1.xml. This seems to be a bug in the Microsoft Business Central side.

<x:tableColumn id="1" uniqueName="Status" name="Status">

   <x:xmlColumnPr mapId="1" xpath="/DataList/ProdOrderLineList/ProdOrderLine/Status" xmlDataType="string" />
</x:tableColumn>
. . .. . . .
<x:tableColumn id="29" uniqueName="Status" name="Status">.  <<== I don't think this is correct. The xPath is pointing to "Put-away Status" field indeed.
   <x:xmlColumnPr mapId="1" xpath="/DataList/ProdOrderLineList/ProdOrderLine/Put_awayStatus" xmlDataType="string" />
</x:tableColumn>
 

(Issue 3) Even if I corrected all the Excel file issues and populated my data (i.e. I added 10 rows to test) and I imported the data, BC would show 0 records to import. This is wrong.

Can you shed some light on what I should do? By the way, I don't know how to report a bug to Microsoft. If you are a MSFT partner and can report a bug to them, can you report the above XML issue #2 to them? It seems these 3 issues are all related. I am an individual developer, and I am not a certified MSFT partner.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

RockwithNav 8,959 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Can you just try with the new excel, simply copy your data in a new excel and then try importing.

Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/

Was this reply helpful? Yes No
Suggested answer

Ramesh Kumar 7,547 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

I would suggest please cache, all the old files and try again. If still not working try RapidStart Assisted Setup

Thanks

Ramesh

If this was helpful, please check the "Does this answer your question?" box and mark it as verified.

Was this reply helpful? Yes No
Suggested answer

Jeffrey Bulanadi 9,112 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!
Hi,

The issues you're seeing with the "Prod. Order Line" configuration package are frustrating, and they do appear to stem from how BC generates the Excel file’s internal XML structure.

Here’s what’s possible:

The duplicate uniqueName="Status" in the XML is likely caused by overlapping field captions — “Status” and “Put-away Status” — both resolving to the same internal name. This confuses Excel and breaks the schema. You can work around this by manually removing one of the conflicting columns from the configuration package before export, or by renaming the field caption temporarily in a sandbox extension.

For the import issue (0 records showing), it’s often due to Excel schema corruption or mismatched field mappings. Even if the data looks fine, BC may reject it silently if the XML structure is invalid. Try exporting a fresh Excel file after removing the problematic fields, then populate only a few rows and re-import to test.

If you’re migrating from GP, consider using XMLport or data migration tools instead of configuration packages for complex tables like 5406. These tools offer more control and avoid Excel’s quirks.

As for reporting the bug: since you’re not a certified partner, you can still raise it via the Dynamics Community thread where others have flagged similar issues. Alternatively, use the BC feedback portal to log it directly — Microsoft monitors that channel for product issues.

Helpful references:

Apply Company Configuration Packages – Microsoft Learn
Definitive Guide to Configuration Packages – BC Geek
Export and Import Data Using Config Packages – Dynamics 365 Lab
XMLport Overview – Microsoft Learn

If you find this helpful, feel free to mark this as the suggested or verified answer.

Cheers
Jeffrey

Was this reply helpful? Yes No
Andrés Arias 5,166 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hello,

One option could be, fill in the information in business central directly and then export excel to validate the completed data.

With that information do the field validation, you are probably missing some field to make the correct import.

I hope I can help.

Regards,

Andres

Was this reply helpful? Yes No
Suggested answer

Sohail Ahmed 11,169 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

This issue happens due to duplicate field captions like "Status" and "Put-away Status" in the config package Excel, causing Excel and BC to break the mapping. A quick workaround is to avoid using Excel export and instead enter data manually or use AL/code to import. If you're not a Microsoft partner, ask a partner to raise this as a bug with Microsoft.

✅ Mark this answer as verified if it helps you.

Was this reply helpful? Yes No