OLAP Grid : Doesn't preserve column and row state

OLAP Grid : Doesn't preserve column and row state

Posted by: prudhvi on 14 September 2017, 12:02 pm EST

• 

  prudhvi

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:02 pm EST

  OLAP grid behaves different compared to Flex Grid for column state

  1. After user increases the width of column by dragging, sorting on the column resets the all the columns width to defaults
  2. When rows are collapsed, sorting a column auto expands all the rows in the OLAP Grid.
  3. After applying layout using olapGrid.columnLayout doesn’t affect the width of column visually.
• 

  manish-gupta1

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:03 pm EST

  Hello Prudhvi,
  
  Thanks for reporting the issue. We are able to replicate the issue at our end for column width changing on sorting and collapsed rows gets expanded on sorting. It requires further investigation so this issue has been escalated to the concerned team for further investigation with tracking is 259119.
  
  We will let you know as soon as we get any update on this.

  You can get width for each column and store in localStorage inside resizedColumn event and set column width again in sortedColumn event as a work around. This will prevent the resizing column on sorting.

  For row expansion on sorting, currently there isn’t a workaround for this.

  ColumnLayout gets applied on PivotGrid but it depends on the Event where you are trying to set it.

  For your reference, please see the attached sample that implements the same.

  Thanks,
  
  Manish Kumar GUpta

  2017/05/Olap_preserveColumnWidth.zip

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 3 January 2018, 5:32 am EST

  HI Prudhvi,
  
  This issue has been fixed and verified with 5.20173.399 build. You may get the prerelease build for testing purpose from here:
  
  http://prerelease.componentone.com/wijmo5/

  We are unable to provide any ETA for next maintenance build release containing this fix. The fix will be included in 399+ release build.

  ~Manish