Issue exporting package to Excel

(0) Share

Report

Posted on by Valentine Motin

Hello everyone,

We're having troubles exporting packages to excel.

I've created different packages with different configurations but every time i get the same error.

"Impossible to find column 1"

Apparently the issue is located in the CopyDataToExcelTable procedure (codeunit 6223), the program doesn't seem to be able to go through the columns of my tables.

I've tried with different standard tables, the extension i'm working with doens't add code on these parts of the code.

The export to rapidstart doesn't have this issue.

Has anyone encounter this same problem ?

Thanks

All responses (3)

Answers (0)

Inogic 24,094 on at

Like (0)

Report

RE: Issue exporting package to Excel

Hi,

Have a look at our 1 Click productivity app – Click2Export with which you can easily export CRM data in Excel templates. For more information, click here.

Thanks!
Magicrevette 215 on at

Like (0)

Report

RE: Issue exporting package to Excel

Hello, I'm Valentine's colleague. We use the Business Central 19.2 On-Premise app + our own app extension that doesn't extend "Config. Package Table" neither "Config. Package Card" page.

During my investigation, I've found that Export package to Excel works perfectly on a Cronus demo database. I've debugged both our app and the Cronus app. I've noticed a difference in behavior in the codeunit 6223 "OpenXML Management", in the procedure CopyDataToExcelTable. In the Cronus, Format(DataColumn.DataType) returns 'System.String'. Our client returns 'System.Int32'. The behavior is different in the case in the procedure WriteCellValue depending on this variable.

I don't understand why this variable has different values from one client to another. They are two different databases, but they both are on the same server, running with the same VSCode client, so the paths to dependencies are the same for both the Cronus and our client.

The error we meet in the screenshot above occurs after one iteration in this loop, in the CopyDataToExcelTable procedure :

Could this difference explains the error ? How can I see wich Dotnet is referenced in each app ?

p.s : the error in english:

Thank you,

Pierre
Community Member Microsoft Employee on at

Like (0)

Report

RE: Issue exporting package to Excel

Hi Valentine,

Can you tell me what app you are using?