at System.Number.ParseInt64(String value, NumberStyles options, NumberFormatInfo numfmt)
at ??.
.??(String , ??? )
at ??.
.(String , ??? )
at ?.? .?(String , String )
at ?.? .
?(? )
at ?.? .[1]?(
? )
at ?.? .?(
? )
at ?.? .Read(
? )
at ?.? .?(‑ , String )
at ?.? .?(‑ , String )
at ?.? .
?()
at ?.? .Read()
at ?.? .(Workbook , LoadOptions )
at Aspose.Cells.Workbook.(Stream , LoadOptions , Boolean )
at Aspose.Cells.Workbook…ctor(Stream stream)
If the file is manually opened with Excel and re-saved from Excel then the conversion succeeds, this is of course not a viable option outside of development.
We have evaluated the presented scenario while using the latest version of Aspose.Cells for .NET 8.6.1.2, and we are able to observe the said exception. At the moment we are not sure what could be causing this issue therefore this incident has been logged in our bug tracking system for thorough investigation. The ticket Id for your reference is CELLSNET-44050. You have to spare us some time before we can provide our analysis results as well as ETA for the fix. We will keep you posted with updates in this regard.
I am afraid, we currently do not have any updates regarding the ticket CELLSNET-44050. In fact, it is currently pending of analysis and is in the queue with other priority tasks. That said, I have requested the concerned member of the product team to schedule the ticket for investigation at earliest possible. We will share the results here as soon as we have completed the analysis or have any updates for you.
This is to update you that the ticket logged earlier as CELLSNET-44050 has been fixed now. We will shortly provide the fix here after ensuring the quality of the build and incorporating other enhancements.
Hopefully, we will provide you a fix on Wednesday or Friday of this week. If the fix is available earlier than this then we will update you on this thread.
We have tested your issue with the following sample code using the latest version: Aspose.Cells
for .NET v8.6.1.6 and found that generated pdf is good. I have attached the output pdf for your reference. Please download it and let us know if there is any error inside it.
We have tested your issue with the latest version Aspose.Cells for .NET 8.6.2 and the output pdf looks fine. All the chart legends are good. Please download the output pdf and highlight your issues by adding comments inside it. You can also provide us screenshots highlighting the issues with red circles. It will help us look into your issue more precisely and we will update you asap.
I am afraid, we are not able to pin point any problem in your generated PDF nor in the PDF we shared earlier in our previous response. That is the reason we asked you to share the PDF after highlighting the problematic areas along with code used for conversion so that we could focus on those areas to assist you further in this regard. If you like, you may also share snapshots of the highlighted problematic areas. Thank you for your understanding and cooperation.
We were able to replicate this issue with the latest version: Aspose.Cells for .NET 8.6.2 and found that some entries of the chart legend get missing while saving to pdf as per your screenshot.
We have logged this issue in our database for investigation. We will look into it and fix this issue. Once the issue is resolved or we have some other update for you, we will let you know asap.
This issue has been logged as
CELLSNET-44079 - Some entries of the chart legend get missing while saving to pdf
This is to inform you
that we have fixed your issue CELLSNET-44079 now. We will soon provide the fix after
performing QA and including other enhancements and fixes.