Using latest AG Grid features in Dash (Roadmap vs. Migration)

Dash Python
1

​Hi everyone,

​I am an AG Grid Enterprise licensee currently preparing to rebuild a major GUI platform.

​I am a long-time fan of Dash, but I’ve hit a bit of a roadblock: I often want to utilize the latest features from AG Grid (such as the AI Toolkit, MCP support, etc.), but these are not yet available or officially wrapped in dash-ag-grid. As I plan this new project, I need to decide whether to stay with the Dash ecosystem or migrate to TypeScript/React to have immediate access to the full AG Grid suite. To help with my decision, I have two questions:

  1. ​Maintenance Roadmap: Is there a general plan or community effort to sync dash-ag-grid with the latest AG Grid major releases more rapidly?

  2. ​Sustainability: For those using Enterprise features, is it practical to bridge this feature gap long-term using dashGridOptions or custom JS, or is a move to a TypeScript stack a more “future-proof” choice for grid-heavy apps?

​I would love to keep my stack in Dash, but clarity on the roadmap is now a deciding factor for my project. Any insights from maintainers or the community would be incredibly helpful.

​Thank you for your hard work on this library!

2

It looks like there’s been recent commits to bring in v34 and v35: Branches · plotly/dash-ag-grid · GitHub. Not sure what the timeline of this looks like though.

1 Like
3

Once v34 or v35 is release, it looks like it may be straightforward to integrate the AI Toolkit with dash-ag-grid since it just needs access gridAPI.

You could use the MCP server now during development to search the upstream AG Grid docs for the version used in dash-ag-grid. That lets AI tools help translate AG Grid examples and APIs into something that works in a Dash app.

Update
@wowwwn and @bweinberg
The dash-ag-grd v34 and v35 are now available as a pre-release. The main reason they aren’t full releases yet is that the dash documentation does not support multiple versions.

3 Likes