amaannawab923 opened a new pull request, #41386: URL: https://github.com/apache/superset/pull/41386
### SUMMARY While poking at the new AG Grid interactive table I noticed that setting a numeric column's **Value Aggregation** to **None** from the column header menu never stuck — after saving and reloading it always snapped back to Sum. The tell was that every other option (Sum/Min/Max/Average) persisted fine; only None was lost. It turns out the grid only persisted column state when the column order, sorts or filters changed — the per-column aggregation function was never part of that change detection. So changing *only* the aggregation didn't trigger a save, and on reload the column fell back to its default (sum-like) aggregation, which made None in particular look like it "reverted to Sum". I pulled the change-detection signature into a small helper and included the per-column `aggFunc` in it, normalizing the None case (null/undefined) to a stable sentinel so it's treated as a real, distinct value rather than dropped. ### TESTING INSTRUCTIONS 1. Create an interactive table in Raw records mode with a numeric column and enable **Show Summary**. 2. Save it and add it to a dashboard. 3. From the column header menu, set **Value Aggregation → None**, save the dashboard and reload. 4. The aggregation should stay on None instead of reverting to Sum. Unit tests added for the signature helper (covers None as null and undefined, and that a real aggregation change is detected). ### ADDITIONAL INFORMATION - [x] Changes UI -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
