XLSB to XLSM Conversion Issue When Target File Name Contains Single Quote in Pivot Table Source

Aspose.Cells Product Family
1

:page_facing_up: Description

I’m encountering a deviation in behavior when converting an .xlsb file to .xlsm using Aspose.Cells for .NET v25.8.0.

The attached file Template-Single-Quote-Issue-Link.xlsb contains a Pivot Table that references an external .xlsb file whose file name includes a single quote (').

:white_check_mark: Expected Behavior (Using Microsoft Excel)

When converting the .xlsb to .xlsm using Microsoft Excel, the relationship in
xl\pivotCache\_rels\pivotCacheDefinition1.xml.rels
correctly retains the single quote in the target file name.

:x: Observed Behavior (Using Aspose.Cells)

When performing the same conversion using Aspose.Cells, the single quote in the file name is duplicated, resulting in two single quotes ('') in the relationship target path.

This causes a mismatch.

:package: Attachments

SingleQuoteIssueWithLink.zip (74.2 KB)
I have included a ZIP file containing:

  • The original template file: Template-Single-Quote-Issue-Link.xlsb
  • The .xlsm file converted using Microsoft Excel
  • The .xlsm file converted using Aspose.Cells

These files demonstrate the difference in how the single quote is handled in the pivot cache relationship.

:mag: Context

This issue seems to have emerged after a recent fix given for the following issue:

:pushpin: Request

Please investigate and fix this deviation.

Let me know if you need any additional details.

2

@vedavyas.velaga

It appears you are encountering an issue with converting an .xlsb file to .xlsm using Aspose.Cells, particularly when the file name includes a single quote. The duplication of the single quote in the relationship target path during conversion is not the expected behavior seen in Microsoft Excel.

Cause:

The issue likely arises from how Aspose.Cells processes file names with special characters, leading to incorrect handling during the conversion process.

Solution:

  1. Check for Updates: Ensure you are using the latest version of Aspose.Cells, as this issue may have been resolved in a more recent release.
  2. Review the Conversion Code: Examine your conversion code to confirm it properly handles file names with special characters, particularly single quotes.
  3. Test with Different File Names: Attempt converting files with different names that do not include single quotes to determine if the issue is specific to that character.

Next Steps:

  1. Contact Support: If the problem persists after these steps, reach out to Aspose support with detailed information about your implementation and the specific files you are working with.

If you require further assistance or a code example for the conversion process, please let me know. I am here to help!

3

@vedavyas.velaga
We have reproduced the issue and opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CELLSNET-58901

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

4

@vedavyas.velaga,

We are pleased to inform you that your issue (Ticket ID: “CELLSNET-58901”) has been resolved. The fix/enhancement will be incorporated in our next release (Aspose.Cells v25.9), which is scheduled for the first half of September 2025. You will receive a notification once the new version is released.

5

The issues you have found earlier (filed as CELLSNET-58901) have been fixed in this update. This message was posted using Bugs notification tool by leoluo