damodhar-admin opened a new issue, #44214:
URL: https://github.com/apache/superset/issues/44214

   Hi Superset Community,
   
   I am using Apache Superset 6.1.0 in Docker.
   
   I have a dashboard with multiple charts. I want each chart to have its own 
filter controls displayed directly above/inside that chart.
   
   For example:
   
   Chart 1 – ICE FUTURES COCOA PRICE
   Filters:
   ASSET TYPE, GROUP, CHAIN, ASSET, GRADE, SPECIFICATION,
   COUNTRY, CONTRACT MONTH, YEAR, EXPIRY DATE, FORWARD MONTH,
   INSTRUMENT TYPE, etc.
   
   Chart 2 – Cocoa FOB prices
   Filters:
   A different set of filters such as COUNTRY, YEAR, GRADE, etc.
   
   Required behavior:
   
   1. Chart 1 filters should affect only Chart 1.
   2. Chart 2 filters should affect only Chart 2.
   3. Each chart can have a different set of filter columns.
   4. The filter controls should be visually associated with their respective 
chart.
   5. I do not want one common global Native Filter Bar for the whole dashboard.
   
   I have checked Native Filters in Superset. I understand that Native Filters 
can be scoped to selected charts, but the filter controls themselves remain in 
the dashboard-level Filter Bar.
   
   My question is:
   
   Does Superset 6.1.0 have any built-in or recommended way to create this type 
of independent, per-chart filter UI?
   
   If not, what is the recommended approach?
   
   Specifically, is there an existing plugin/extension mechanism or frontend 
component that can be used to render filter controls inside each chart tile 
while keeping the filter state and query isolated to that chart?
   
   I would prefer to use existing Superset functionality wherever possible and 
avoid maintaining a large fork.
   
   Environment:
   - Apache Superset 6.1.0
   - Docker deployment
   - Dashboard: COCOA
   - Multiple charts/datasets
   
   Any guidance or examples from the Superset community would be greatly 
appreciated.
   
   <img width="1600" height="709" alt="Image" 
src="https://github.com/user-attachments/assets/414d5e96-6fed-4f35-8ded-aadb537fc1e6";
 />


-- 
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]

Reply via email to