Bug description
(async () => {
try {
await embedDashboard({
id: DASHBOARD_ID,
supersetDomain: SUPERSET_URL,
mountPoint: document.getElementById("dashboard") as HTMLElement,
fetchGuestToken,
dashboardUiConfig: {
hideTitle: false,
hideTab: true,
hideChartControls: false,
filters: { visible: false, expanded: false },
urlParams: { native_filter_key: "" },
},
iframeSandboxExtras: ["allow-same-origin", "allow-scripts", "allow-popups"],
});
} catch (err) {
const errorMessage = err instanceof Error ? err.message : "Unknown error occurred";
setError(errorMessage);
ToastService.addMessage(`Error embedding dashboard: ${errorMessage}`, { variant: "error" });
}
})();
}, [token]);
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
I found some similar discussions that might be relevant to your issue with filters not hiding in the embedded dashboard:
- Unexpected JSON error when embedding - This discussion is still open and might provide insights into embedding issues.
- Hide filter using filter name on embedded dashboards feature - This is another open discussion that might be related to your problem.
- Embedded dashboard charts "Applied Filter" not visible - This discussion is also open and could be relevant.
Regarding your issue, ensure that the filters property in the dashboardUiConfig is correctly set to control the visibility and expansion state of filters. The filters configuration should work as intended to hide filters when set to { visible: false, expanded: false } [1]. If the filters are still not hiding, it might be worth checking if there are any recent changes or updates in the Superset codebase that could affect this functionality [2].
To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other
Comment From: rusackas
Maybe @Vitor-Avila can spot something amiss here.
Comment From: Vitor-Avila
@devyash786 which Superset version are you currently running?
Comment From: saraburns1
@Vitor-Avila I'm seeing this with version 4.1.1
Comment From: Vitor-Avila
@saraburns1 it should be fixed with: https://github.com/apache/superset/pull/29422. It seems this is tagged with 5.0, so I believe it would be included in that release.
Comment From: rusackas
Indeed 29422 was part of 5.0, so I'll close this out.