We have tested .numbers format document with all the features we use for Excel and we see lot of discrepancies related to sheets, shapes, graphics etc.
I am attaching a sample console application which has two files one is .numbers format file and another excel file which is exported as .xlsx in MacOS’s Numbers application.
Aspose.Numbers.Documents.zip (1.6 MB)
Below are the few observations for the attached .number format file after conversion:
- The first sheet, Export Summary, is missing in the converted file.
- Data from all sheets whose names begin with the same word (e.g., Team sheet - Teamsheet, Team sheet - Team Management, Team sheet - Drawings) is being combined into a single sheet named Team sheet.
- Shapes are not displaying correctly in the file after conversion to .number format for the above sheets. We display shapes by storing them as PNG files, but somehow the PNG files are losing the color information.
- One of the shape (Caption) of sheet1 is missing for .number converted file
- Few Graphics are missing i.e., not read.
- The data from the sheets Budget - Cost Breakdown, Budget - Player Count, Budget - Cost Per Player, and Budget - Drawing is being merged into a single sheet named Budget
@shivanandchikkalli
It sounds like you’re encountering several issues when converting .numbers files to .xlsx format using Aspose. Here’s a breakdown of your observations and actionable steps to address them:
-
Missing Sheets: If the “Export Summary” sheet is missing, ensure that the sheet is not hidden in the original .numbers file. Additionally, check your conversion code for any settings that might exclude certain sheets.
-
Combined Sheets: The merging of sheets with similar names into a single sheet could be due to how the library handles naming conflicts. To prevent this, explicitly set unique names for each sheet during the conversion process.
-
Shape Display Issues: If shapes are not displaying correctly and PNG files are losing color information, review the image format and color settings in your conversion code. Ensure that images are processed correctly and that color profiles are maintained.
-
Missing Shapes: For the missing caption shape, verify that it is not being excluded during the conversion. Inspect the properties of the shape in the original file to ensure compatibility with the .xlsx format.
-
Graphics Not Read: If certain graphics are not being read, confirm that they are in a supported format and that your conversion settings allow for the inclusion of all graphic types.
Next Steps:
- Review your conversion code to ensure that all sheets and shapes are being processed correctly.
- Test with a simplified version of your .numbers file to isolate the issue.
- Consult the Aspose documentation for specific settings related to .numbers to .xlsx conversions that may resolve your issues.
If you continue to experience discrepancies, reach out to Aspose support with detailed information about your conversion process and the specific files you’re working with.
Please let me know if you need further assistance!
We have tried with the LoadFormat value as Numbers as below, but still we’re able to observe the discrepancies.
var loadOptions = new Aspose.Cells.LoadOptions(LoadFormat.Numbers);
var workbook = new Aspose.Cells.Workbook(stream, loadOptions);
Let us know if we need to make more changes to support the .numbers format.
@shivanandchikkalli
When you export a .numbers
file to an .xlsx
file on a Mac, the Numbers application provides export options such as “One sheet per worksheet”, “One table per worksheet”, and “Include summary worksheet”.
Your choice among these options will result in different .xlsx
files being generated.
When using Aspose.Cells to export a Numbers file to .xlsx
, we only support mapping each worksheet in the source .numbers
file to a corresponding worksheet in the .xlsx
file — that is, the “One sheet per worksheet” option mentioned above.
Finally, when exporting charts and shapes from .numbers
to .xlsx
, Aspose.Cells still requires further improvement. We have created the following ticket to track this.
Thank you!
We have 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-58877
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.