Header filter

[queensgambit9]

When loading a state the values in the filter (range) seems to be limited to the matches found.
Can this be changed to always show all (turn cascading off)?

Use case could be when you want to change a filter in a saved state that is different from match.

Also, is there a way to convert old states (5.1.0) to work with 5.6.0?

[paramvir]

While loading a state, column filter values can be skipped by removing filter.crules from default value of stateColKeys

Code: [Select]

  stateColKeys : { filter: [ 'mode' ] }

https://paramquery.com/pro/api#option-stateColKeys

state saved in 5.1.0 is structurally different from 5.6.0.

[queensgambit9]

Thanks, sorry if a bit unclear.

I do not want to remove the filter values. I am refering to the options in the filter dropdown.
They seem be locally loaded when the state is loaded. But I want the options from DB.

Ex:
col1, col2
value1, valuea
value2, valueb

Saving a state with with col1 filter = value1.
Available options for filter in col1 should now still have value1, value2 (not only value1).

Currently if you clear a column filter after loading a state the options are not updated from DB. Even though I have populated them from DB when creating the grid.

[paramvir]

loadState is called during create event ( synchronously ), and options are loaded from db asynchronously which occurs after load state anyway, so the problem shouldn't arise.

It can be verified by adding this

Code: [Select]

complete: function(){
        this.getColumn({dataIndx:'ShipRegion'}).filter.options = [{ShipRegion: 'China'}, {ShipRegion: 'Japan'}]
this.refreshHeader();
}

in this demo: https://paramquery.com/pro/demos/grid_state

I see the options in ShipRegion column filter as 'China' and 'Japan'.

Hope this helps.

[queensgambit9]

Thank you.
I think the issue is that I use remote paging and have to select all distinct values to populate the options. I do this in create event currently...
But how do I instruct grid to always use the db options above and override the default that populate options based on the available data currently in grid?

[paramvir]

When filter options are assigned directly like column.filter.options = [...], those are instructions to the grid to always use those options instead of populating options based on the available data currently in grid. It doesn't matter whether it's local or remote paging.

Just ensure to assign filter options after loadState.

If you are facing issues please share a small test case via jsfiddle.

[queensgambit9]

Thanks, works fine.