Bug with Pivot tables starting with 8.6.2

Aspose.Cells Product Family
1

This is regarding smart marker processing, rather than using the API. I have a workbook with 2 tabs. One is loaded with data at runtime, and the other is a pivot table which points to the other tab as a data source. My data tab looks like this:

&=Table.Col1 | &=Table.Col2 | &=Table.Col3

My pivot table sets the data source to this row. At runtime, the smart marker processing will insert the # of rows needed, and it will cause the pivot’s data source range to expand. This worked great until 8.6.2 was released. The pivot table will not refresh, first of all, but the data source range will also not expand with the data. I just tried with 8.6.3 and the same problem still exists. When I go back to 8.6.1, it works. So right now, I’m stuck at 8.6.1.

Sample file is attached.
2

Hi,


Thanks for providing us template file.

Could you please create a simple console application (runnable), zip it and post us here to reproduce the issue with v8.6.3, we will check it with v8.6.1 and v8.6.3 soon. Also, kindly use dynamic Data table(s) as data source for the markers in your code, so we could evaluate your issue properly and log your issue (if found) into our database (as a regression).

Thank you.
3

Hi Amjad,

I’ve created a small program and attached it. If you run with 8.6.1, you’ll see that the “Pivot” tab properly loads the dynamically loaded data from the “Table1 Data” tab. If you move up to 8.6.2 or 8.6.3, you’ll see that the “Pivot” tab no longer populates. And even if you click “Refresh” on it, you’ll see that it only picks up the first row of data from “Table1 Data” rather than all rows (the dynamic row expansion also stopped working).
Thanks for your attention.
-Chris
4

Hi Chris,


Thank you for sharing the sample project.

I have executed the project against Aspose.Cells for .NET 8.6.1 & 8.6.3 without observing any difference between the two resultant spreadsheets. Could you please have a look at the attached files? Please find the details of the spreadsheets as follow.

  • AsposeCellsBug.Template.Generated.20160113.111445.xlsx: Generated with Aspose.Cells for .NET 8.6.3.
  • AsposeCellsBug.Template.Generated.20160113.111755.xlsx: Generated with Aspose.Cells for .NET 8.6.1.

Could you please share more details about your environment so we could give this scenario another try on our side?
5

I have reproduced it on many machines. I have a Windows 7 desktop, but I’ve also run this report on several of our application servers. I have attached 2 versions of my program, to ensure there’s no confusion. If you look in the bin\Debug folder for each version, you’ll see the output that I got. I am guessing that your local run did not properly use the right version of Aspose.Cells.


Also, are you telling me that the output that you got in your tests is what you really want your software to provide? To me it’s not consistent with how the product performs, and you should have seen that the output that you received is not what a user would want or expect.

Until this is addressed, I have to stay on version 8.6.1, which I do not like to do. Or I have to hack my template files so that the pivot table points to a huge range of empty cells, such as A1:EE30000
6

Hi Chris,


Thank you for writing back.

You are correct about the project not referencing the recent Aspose.Cells for .NET assembly when I last tested the scenario on my side. Please note, both resultant spreadsheets attached to my previous response show the correct result, that is; both spreadsheets shows the Pivot Table with data populated from A2:D1001, however, I perhaps didn’t clean build the project during that testing session therefore the results are invalid. Please accept my apologies for the inconvenience.

I have retested the scenario today while using Aspose.Cells for .NET 8.6.1, 8.6.3 & 8.6.3.4 (latest) and I am able to replicate the issue while using 8.6.3 & 8.6.3.4, that is; the smart marker in the Pivot Table is not getting processed unless I manually refresh the Pivot Table in Excel application, even in this case only one row of data is getting populated. Whereas if same scenario is repeated against Aspose.Cells for .NET 8.6.1, the results are expected. That said, I have logged an investigative ticket with Id CELLSNET-44172 in our bug tracking system, and have requested the concerned member of the product team to review this case to provide the justification for the said behaviour change. Please spare us little time for proper analysis. In the meanwhile, we will keep you posted with updates in this regard.
7

Any update on this? I cannot upgrade the software until it’s fixed. If I can’t upgrade, then there’s no need to renew the license. Please advise, thank you.

8

Hi Chris,


I am afraid, we haven’t received updates regarding the ticket logged earlier as CELLSNET-44172. However, we have requested the concerned member of the product team to share insight of this problem and preferably an estimated time frame for the fix, As soon as we get any news we will post here for your kind reference.
9
Hi,

This is to inform you that we have fixed your issue "CELLSNET-44172" now. We will soon provide the fix after performing QA and including other enhancements and fixes.

Thank you.
10

Hi,


Please try our latest version/fix: Aspose.Cells for .NET v8.8.2.1 (attached).

We have fixed your issue now.

Let us know your feedback.

Thank you.
11

The issues you have found earlier (filed as CELLSNET-44172) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by Aspose Notifier.