we are using on old Templatete with a formular in a pie chart like this
=‘C:\Users\someone\Desktop[NM v2 - Values.xlsx]M&A’!F42
This is saved in pptx like this
‘[1]M&A’!F42Structure‘[1]M&A’!G420.5
The Aspose.Slides 20.3 and older shows always the Fallback Value “Structure”.
Now since 20.4 and in the current Version 21.6 we got the following error:
The cell ‘Sheet1’!A2 contains an unsupported formula.
This happens on save Methed
Presentation FPres
…
FPres.Save(ms, SaveFormat.Pptx);
@Thomas_Meinusch,
Thank you for the issue description. To investigate the error on our side, please share the following:
This is an example Template
PieChartWithFallback.pptx.zip (33.9 KB)
The exception on save with Aspose looks like this:
bei Aspose.Slides. .()
bei Aspose.Slides. .kke8x56u632qjmq6pcqbamquzfqx5x3v ()
bei Aspose.Slides.Charts.ChartDataCell.get_Value()
bei Aspose.Slides.Charts.ChartCategory.get_Value()
bei Aspose.Slides. .(IChartCategoryCollection , )
bei Aspose.Slides. .(IChartCategoryCollection , , ChartData )
bei Aspose.Slides. .(IChartSeries , , , )
bei Aspose.Slides. .(IChart , , )
bei Aspose.Slides. .(IChart , , )
bei Aspose.Slides. .(IChart , , , )
bei Aspose.Slides. .(IChart , , )
bei Aspose.Slides. .(IChart , , )
bei Aspose.Slides. .(IChart , , )
bei Aspose.Slides. .(IShape , , , )
bei Aspose.Slides. .(IShape , , , )
bei Aspose.Slides. .(IGroupShape , , , )
bei Aspose.Slides. .(IBaseSlide , , )
bei Aspose.Slides. .(ISlide )
bei Aspose.Slides. .( , ISlide , )
bei Aspose.Slides. .(IPresentation , Stream , PresentationTypeEx , IPptxOptions , InterruptionToken )
bei Aspose.Slides.Presentation.(Stream , PresentationTypeEx , IPptxOptions )
bei Aspose.Slides.Presentation.Save(Stream stream, SaveFormat format, ISaveOptions options)
bei Aspose.Slides.Presentation.Save(Stream stream, SaveFormat format)
bei EfsService.PptxExporter.Generate(XDocument doc, Boolean debugMode, Boolean makePdf, String addPath) in C:\Users…\PptxExporter.cs: Zeile401
After observing the issue on our end, I have created a ticket with ID SLIDESNET-42690 in our issue tracking system to further investigate and resolve the issue. This thread has been linked with the issue so that you may be notified once the issue will be fixed. I also request you to please provide the working sample code reproducing the issue on your end.