dosubot[bot] commented on issue #36791: URL: https://github.com/apache/superset/issues/36791#issuecomment-3680977806
<!-- Answer --> In Superset 5.0.0, dashboard filters and cross-filtering are managed directly in the dashboard UI, and filter state is global to the dashboard—meaning filters persist across tabs and affect all charts in their scope, including table charts. When you apply a filter on one tab and switch to another, the filter state is preserved and should trigger a data refresh for affected charts, including those on other tabs. Table charts receive the current filter state as a prop and will show no data if the filters exclude all rows or if there is a filter state issue ([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/plugins/plugin-chart-table/src/TableChart.tsx#L255-L1243), [dashboard logic](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/dashboard/components/Dashboard.jsx#L90-L285)). There is a known bug in 5.0.0 where dashboard metadata changes (like enabling cross-filters or updating filter scopes) may silently revert if the dashboard has owners but no tags attached. This can cause filter settings to not persist, leading to inconsistent filter behavior or charts (especially tables) not displaying data as expected. The usual workaround is to add a tag to the dashboard via the API, but this does not always resolve the issue in 5.0.0 ([details and workaround steps](https://github.com/apache/superset/issues/34688)). This bug is fixed in newer versions. For troubleshooting: - Check your filter scoping in dashboard edit mode and ensure filters are set to apply to the affected table charts/tabs. - Try adding a tag to your dashboard using the API and then saving your filter settings again. - Review Superset logs for any errors when the table charts fail to display data. - If the issue persists, consider upgrading to a newer Superset version where these bugs are resolved. If you can share your dashboard metadata or filter configuration, I can help interpret it and suggest more targeted steps. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/c3238026-7a28-402e-8c3d-4f9c143b7a7b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/c3238026-7a28-402e-8c3d-4f9c143b7a7b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/c3238026-7a28-402e-8c3d-4f9c143b7a7b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/c3238026-7a28-402e-8c3d-4f9c143b7a7b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c3238026-7a28-402e-8c3d-4f9c143b7a7b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/c3238026-7a28-402e-8c3d-4f9c143b7a7b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c3238026-7a28-402e-8c3d-4f9c143b7a7b?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=In%20Superset%205.0.0%2C%20dashboard%20filters%20and%20cross-filtering%20are%20managed%20directly%20in%20the%20dashboard%20UI%2C%20and%20filter%20state%20is%20global%20to%20the%20dashboard%E2%80%94meaning%20filters%20persist%20across%20tabs%20and%20affect%20all%20charts%20in%20their%20scope%2C%20including%20table%20charts.%20When%20you%20apply%20a%20filter%20on%20one%20tab%20and%20switch%20to%20another%2C%20the%20filter%20state%20is%20preserved%20and%20should%20trigger%20a%20data%20refresh%20for%20affected%20charts%2C%20including%20those%20on%20other%20tabs.%20Table%20charts%20receive%20the%20current%20filter%20state%20as%20a%20prop%20and%20will%20show%20no%20data%20if%20the%20filters%20exclude%20all%20rows%20or%20if%20there%20is%20a%20filter%20sta te%20issue%C2%A0%28%5Bsource%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/plugins/plugin-chart-table/src/TableChart.tsx%23L255-L1243%29%2C%C2%A0%5Bdashboard%20logic%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/dashboard/components/Dashboard.jsx%23L90-L285%29%29.%0A%0AThere%20is%20a%20known%20bug%20in%205.0.0%20where%20dashboard%20metadata%20changes%20%28like%20enabling%20cross-filters%20or%20updating%20filter%20scopes%29%20may%20silently%20revert%20if%20the%20dashboard%20has%20owners%20but%20no%20tags%20attached.%20This%20can%20cause%20filter%20settings%20to%20not%20persist%2C%20leading%20to%20inconsistent%20filter%20behavior%20or%20charts%20%28especially%20tables%29%20not%20displaying%20data%20as%20expected.%20The%20usual%20workaround%20is%20to%20add%20a%20tag%20to%20the%20dashboard%20via%20the%20API%2C%20but%20this%20does%20not%20always%20resolve%20the%20is sue%20in%205.0.0%C2%A0%28%5Bdetails%20and%20workaround%20steps%5D%28https%3A//github.com/apache/superset/issues/34688%29%29.%20This%20bug%20is%20fixed%20in%20newer%20versions.%0A%0AFor%20troubleshooting%3A%0A-%20Check%20your%20filter%20scoping%20in%20dashboard%20edit%20mode%20and%20ensure%20filters%20are%20set%20to%20apply%20to%20the%20affected%20table%20charts/tabs.%0A-%20Try%20adding%20a%20tag%20to%20your%20dashboard%20using%20the%20API%20and%20then%20saving%20your%20filter%20settings%20again.%0A-%20Review%20Superset%20logs%20for%20any%20errors%20when%20the%20table%20charts%20fail%20to%20display%20data.%0A-%20If%20the%20issue%20persists%2C%20consider%20upgrading%20to%20a%20newer%20Superset%20version%20where%20these%20bugs%20are%20resolved.%0A%0AIf%20you%20can%20share%20your%20dashboard%20metadata%20or%20filter%20configuration%2C%20I%20can%20help%20interpret%20it%20and%20suggest%20more%20targeted%20steps.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/36791) -- 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]
