I’m trying to combine two workbooks that contains some pivot charts with a template applied to them. When combining the workbooks, the styles of the charts are reseted to “Style2” on Excel.
I’ve applied the template chart on the original chart, but it is not applied on the output file.
This issue also happens when refreshing the associated pivot table.
As you can see in the example_1.xlsx and example_2.xlsx files, neither the charts keep their styles, nor the pivot table keeps the “banded rows” option in SheetA.
Thank you for sharing the sample spreadsheets and code snippet.
We have evaluated the presented scenarios while using the latest version of Aspose.Cells for .NET 8.5.0, and we are able to replicate both of said cases. We have logged the following tickets in our database for further investigation and correction purposes.
CELLSNET-43726: Combining workbooks change the chart style
CELLSNET-43727: “Cannot edit a PivotTable in group edit mode” Excel warning while loading combined result. Please check attached snapshot for your reference.
CELLSNET-43728: Refreshing the PivotTable with new data changes the chart style
Please spare us some time to properly analyze the scenarios to pin point the problem cause. In the meanwhile, we will keep you posted with updates in this regard.
What about the “banded rows” style in pivot tables? When combining two workbooks it doesn’t keep the “banded rows” option on true…
You have to look at SheetB on example_1.xlsx (PivotTable1). This option is true in the wbB.xlsx file, but the after the combination of workbooks it is set on false.
Sorry, I missed this point to check during my previous testing. Now I am able to verify that PivotTable’s Branded Rows option selection is lost while combining the workbooks with Aspose.Cells for .NET 8.5.0. I have logged it separately as CELLSNET-43735 for further investigation. As soon as we have completed the analysis, we will share our results here for your reference.
Sure, we will inform you as soon as we have completed the preliminary analysis of the logged tickets. Please note, all of the tickets are currently pending for analysis and are in the queue with other priority tasks.
We need more time to properly analyze the scenarios to pin point the problem cause so please spare us some time for it. By the way, among the 4 tickets attached to this thread, one ticket (CELLSNET-43727) has been marked resolved, whereas other tickets are currently in analysis phase. As soon as we have further updates regarding the unresolved tickets, we will post here for your kind reference.
This is to update you regarding the tickets attached to this thread. We will try our best to provide the fix for most of the issues reported in this thread by the 2nd week of July 2015.
This is to update you regarding the ticket logged earlier as CELLSNET-43735. Hopefully, we will be able to provide the fix during the 3rd week of July 2015.