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

Notifications

Announcements

No record found.

Community site session details

Community site session details

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

Configuration Package Table Export Error

(1) ShareShare
ReportReport
Posted on by 2
Hi,
 
I have two BC 21.3 instances on different databases and when I try to export table to excel from one it results in error:
A call to Microsoft.Dynamics.Nav.OpenXml.Spreadsheet.WorkbookWriter.CreateSchemaFromOpenXmlUnknown failed with this message: The type of one or more arguments does not match the method's parameter type.
But when I try the same export from the second instance, it works. I tried to restart both instances so they have same DLLs loaded.
 
Error is thrown from codeunit 6223 /OpenXML Management/, line 391:
Schema := WrkbkWriter.CreateSchemaFromOpenXmlUnknown(OpenXmlUnknownElement);

I also checked that both files that variable StreamText are the same.
 
I am testing on configuration package with only one table 270.
 
Thank you for the help
 
I have the same question (0)
  • MC-07050738-0 Profile Picture
    1 on at
    Hi, hope you are doing fine.
     
    Facing the same issue, have you found a fix for yours?
  • Suggested answer
    KasparsSemjonovs Profile Picture
    4,780 Super User 2025 Season 2 on at
    Hi,
    could it be that You have a fresh Office installation, and user has selected to use OpenDocument format, instead of Open XML format? This can be chosen when Excel is first time opened after installation. 
    If so - try to go to Excel Options, under Save section change "Save files in this format" - to Excel Workbook.

    Solved: The Office Open XML Cannot Be Opened [Full Guide] - EaseUS

  • MC-07050738-0 Profile Picture
    1 on at
    Thanks for the idea, Kaspars!
     
    Unfortunately not the case. Setup of Excel is identical to yours and the issue is not reproducible in case I'm switching the database to demo one, so I would suggest that the problem is somewhere in the data.
  • Suggested answer
    HVGEEL Profile Picture
    308 on at
    I agree that this sounds like a data-problem, not a technical issue.
     
    Have you tried triming down the output to the fields that are 100% necessary, because from what I read, you are simply dumping the table, without (a) a table filter or (b) excluding fields from the output.
     
    Obviously, that is not a fix for the technical issue, but is might point you to where the issue is coming from.
    Iterate exporting, excluding 'suspicious' fields one at the time.
     
    Tedious? I know.
    But sometimes that is all it takes.
  • ondix Profile Picture
    2 on at
    Hi,
     
    after I upgraded both databases to BC23.4, the problem is solved. I don`t know whether it was data-related (users could have possibly edited the records) or it was technical-related (version-specific). As far as I remember, I tried to export primary key field only with the same result, but I can`t reproduce it.
     
    Thank you for your replies.
    Best regards,
    ondix

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

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

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,066

#2
YUN ZHU Profile Picture

YUN ZHU 658 Super User 2025 Season 2

#3
Sumit Singh Profile Picture

Sumit Singh 595

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans