Closed qianjixin closed 1 year ago
This could be related to the issue in my post about the column state acting oddly when swapping between layouts with grids.
Seems like it could be trying to apply the filter to a non-existent column.
Thanks for bringing this up.
When you say, downgrading, what do you mean? Which version of dag?
Hi, this is using dash-ag-grid==2.0.0a5, as installed via pip (also happens when I build the component from source). By downgrading I mean, I edited the 3 AG Grid dependencies in package.json to look like:
"ag-grid-community": "^28.0.0",
"ag-grid-enterprise": "^28.0.0",
"ag-grid-react": "^28.0.0",
What about bumping up to the latest version? I believe we are a minor release behind.
I tried out the latest 29.2.0 packages and the issue is still there. Looks like it's triggered by v29 Column Set Filter Improvements. I'll keep testing to try and get more details.
Just one more piece of data - This example app fails in 2.0.0a3, but works fine in a1 and a2.
In a3 we upgraded from 29.0.0 to 29.0.1.
I tried out the latest 29.2.0 packages and the issue is still there. Looks like it's triggered by v29 Column Set Filter Improvements. I'll keep testing to try and get more details.
We believe that this issue was fixed in AG Version 29.2 after being introduced in v29.1.
Thanks @StephenCooper 🎉
Seems to be working after bumping to 29.2, this should be available in the next release.
Please reopen if you continue to have issues.
Using a multi-page Dash app, after interacting with an agSetColumnFilter (deselecting, selecting options) I try to switch pages but the page freezes and CPU usage goes to ~100%. I have also noticed this with agMultiColumnFilter. Downgrading AG Grid packages to v28 seems to alleviate this specific issue. This is possible due to some filter changes in v29. Simple example: