Need a special offer?Find out if your project fits.
+

Still wrong alignment in Excel export version 2.7.22

Resolved
Miguel Maldonado asked on January 3, 2020

Hi!
 
We found a strange behaviour when exporting the report to Excel, related to the alignment of the cells.
 
We are following follow these steps:

  1. Connect to the data source (MSAS in our case). Configure some dimensions and measures. The default alignment on the pivot cells is to the right. However when we use the Export option (using the API: pivot.exportTo(“excel”);), in the downloaded Excel file the cells with values are aligned to the left. I checked the formatting options (pivot.getFormat()) just before the download and the textAlign property has the value “right”.
  2. Then we change the cell format options (with pivot.toolbar.formatCellsHandler();). By default “right” alignment is selected. If we change it to “left”, apply, and then change it to “right” again, the pivot table looks (logically) the same as in the beginning, but if we then export it to Excel, the cells are now correctly aligned to the right.

It looks like the first time it doesn’t export the “right” alignment to Excel, and it only starts applying the settings after you change them. Actually, if we open the formatting menu, change any other option (not the alignment) it applies correctly on the pivot and also on the downloaded Excel, but the Excel cells are still aligned to the left.
 
We have the version 2.7.22
 
Thank you very much for your help.

3 answers

Public
Miguel Maldonado January 3, 2020

Hi!

Doing a second revision we discovered that this error only occurs in Internet Explorer 11 (version 11.914)

Thank you very much for your help.

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster January 3, 2020

Hello, Miguel,
 
Thank you for reaching out to us.
 
We would like to kindly inform you that our team did not manage to reproduce the described issue on the current version of Flexmonster 2.7.22, including tests using Internet Explorer 11.
 
It would be very useful for our investigation if you could modify the JSFiddle we have created trying to reproduce the problem.
 
Kind regards,
Illia

Public
Miguel Maldonado January 7, 2020

Hi Illia.
 
This problem is solved.
We had been working with a previous version (2.7.21).
Update to 2.7.22 version solve this problem.
 
Best regards.
Miguel

Please login or Register to Submit Answer