Hi Praveen Singh
Yes this is a known class of issue, and your diagnosis is essentially correct. Both SONACA Advanced Excel and the Data Importer run on Apache POI under the hood. The writer (Advanced Excel) and the reader (Data Importer) have different tolerance for OOXML package structure. Excel's importer is strict about the package; the file you generate is valid-enough-to-open but not fully standards-compliant.When you add multiple sheets, the most likely culprits are [content_type].xml / workbook.xml.rels not correctly declaring every sheet part and its relationship ID (single sheet = one trivial relationship; multi-sheet exposes the gap).sharedStrings.xml count/uniqueCount mismatch, or inconsistent inline-vs-shared string handling across sheets.File written with a streaming writer (SXSSF) that doesn't fully finalize workbook metadata.
When you open in Excel and Save, Excel rewrites a clean, normalized OOXML package — which is exactly why the import then succeeds. This is the same root cause behind the Data Importer/Excel Importer's own warning message: if the file was not created with Microsoft Excel for desktop, try opening the file with Excel and saving it with the same name before importing.
Answering your question
Hack which you can worth trying is Add a post-export Java action that opens the generated file with POI's WorkbookFactory and writes it straight back out. This rebuilds the package exactly like Excel's Save
try (Workbook wb = WorkbookFactory.create(inputStream);
OutputStream out = new FileOutputStream(normalizedFile)) {
wb.write(out); // POI rewrites a clean, compliant package
}
I hope this helps