Get Free Trial

TableSizes mapping from 2.2

Maya Shavin asked on March 15, 2017

As written in Migrate guide, these following fields are mapped to 2.3 report as tableSizes properties accordingly:

columnHeaderSizes --> tableSizes.columns
columnSizes --> tableSizes.columns

rowFilterSizes --> tableSizes.rows
rowHeaderSizes --> tableSizes.rows
rowSizes --> tableSizes.rows

My question: take tableSizes.columns for example, both columnHeaderSizes and columnSizes are mapped to tableSizes.columns, so how exactly are they mapped? If in old report there are columnHeaderSizes and columnSizes defined differently, which array will be mapped to tableSizes.columns explicitly?

1 answer

Tanya Gryshko Tanya Gryshko Flexmonster March 15, 2017

Hello Maya,
Thank you for the question. Both arrays columnHeaderSizes and columnSizes will be inside tableSizes.columns. I would like to explain the difference between columnHeaderSizes and columnSizes. With columnHeaderSizes we define the width for the headers of the table. So, when mapping to tableSizes.columns , it would be the array of objects containing width and idx (index of the column). With columnSizes we define the width based on data tuples. When mapping to tableSizes.columns, it would be the array of objects containing width and tuple (unique names that identify the column in the table based on data in it). For more details about tableSizes please refer to our documentation. Please let me know if you need more details about this.

Please login or Register to Submit Answer