CustomUI is lost after conversion xlsb -> xlsm


#1

Hi Aspose,

During conversion CustomUI.zip (4.9 KB) to xlsm format, CustomUI is lost. Aspose.Cells 18.7.1

Best regards,
Alex Shloma


#2

@licenses,

Thanks for your query.

Please provide more details about this issue along with the description, sample code and supporting images (if any). We will reproduce the problem and provide our feedback after analysis.


#3

@licenses,

We have further investigated the data and found that the size of customUI.xml in the file is zero, so they are ignored.


#5

Thank you for investigation - you are right, size is 0.

Let me use another document to describe the issue: When I convert the document with Custom Ui xml from xlsb to xlsm, the document becomes corrupt for OpenXml Sdk. OpenXml productivity tool says on opening:
image.png (6.9 KB)

Investigations shows that in case of Aspose document, the OpenXml property
doc.RibbonAndBackstageCustomizationsPart is not null (but broken) while in case of Excel document it is null.
Debugger shows such properties for this object:
image.jpg (54.4 KB)

Please see AllFiles.zip (2.2 MB)

Best regards,
Alex Shloma


#6

@licenses,

We were able to observe the issue but we need to look into it more. We have logged the issue in our database for investigation and for a fix. Once, we will have some news for you, we will update you in this topic.

This issue has been logged as

CELLSNET-46483 - Error after converting document with Custom Ui xml from xlsb to xlsm

#7

@licenses,

Please try our latest version/fix: Aspose.Cells for .NET v18.11.5 (attached)

Your issue should be fixed in it.

Let us know your feedback.
Aspose.Cells18.11.5 For .Net2_AuthenticodeSigned.Zip (4.7 MB)
Aspose.Cells18.11.5 For .Net4.0.Zip (4.7 MB)


#8

Hi Amjad,

Unfortunately issue from my previous comment is still present.

Best regards,
Alex Shloma


#9

@licenses,

You are right, OpenXML SDK productivity tool still shows the error on the generated file by Aspose.Cells. We have recorded your comments and will look into your issue to provide our feedback after further discussions.

We are sorry for any inconvenience caused!


#10

@licenses,

We fixed your issue now. We will provide you the fix (the version number might be v18.11.6) in the next few days after performing QA and incorporating other enhancements and fixes.


#11

Thank you for letting us know.