[D] Enabling automatic FilterState management for Embedded Dashboards [superset]

["martinikf (via GitHub)" <gi...@apache.org>]

GitHub user martinikf created a discussion: Enabling automatic FilterState management for Embedded Dashboards

Hi all,

I'm looking for a way to use FilterState in embedded dashboards.

When viewing dashboards through the Superset frontend, the FilterState API endpoints are called on dashboard load and when filters are applied. If the page is accessed without the native_filters_key URL parameter, a new filter state is created and its key is inserted into the URL. This key can then be reused in other sessions to apply previously saved filters on dashboard load.

However, in embedded dashboards, the FilterState endpoints are not called. As a result, no filter state is created or updated.

Is it possible to enable this behavior for embedded dashboards? Or is the only option to manually call the FilterState API?

The goal is to allow the parent (host) application to extract the FilterState key from the iframe src, store it, and reuse it in other sessions via the URL parameter (which already works). This would enable persistent filter state per user on the host web app.

Thanks in advance!

GitHub link: https://github.com/apache/superset/discussions/34151

----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org