Dashboards Filter API Behavior Discrepancy with App Studio (Removing filters)

I'm encountering an issue with the domo.filterContainer()
API in Domo App Studio. When I apply filters (Custom filter brick) using this API within my app, they work as expected. However, when I clear the filters using the UI (e.g., by clicking a "Clear All" button or removing individual filter selections), the filters are not actually cleared from the underlying data. Instead, it seems they are being set on the app's filters in App Studio, and I have to manually clear them using the page filtering options.
This behavior is different from what I observe in Domo dashboards, where clearing filters in the UI properly removes them completely without any manual update in the page filters.
Here's the relevant code snippet:
JavaScript:
function clearFilter() { enableLogging && console.log('Clearing all filters'); selectedColumns =; // Add App Studio-specific double cleardomo.filterContainer(, "REPLACE"); setTimeout(() => domo.filterContainer(, "REPLACE"), 50); renderSelectedFilter();saveToLocalStorage();} // Session cleanup for App Studio window.addEventListener('beforeunload', () => { domo.filterContainer(, "REPLACE");// ...}); // Filter sync handlerdomo.onFiltersUpdate((filters) => { if (filters.length === 0 && selectedColumns.length > 0) {// ...}});
As you can see, I've already tried:
Calling domo.filterContainer(, "REPLACE")
to clear the filters.
Adding a setTimeout
to call domo.filterContainer
again, as a workaround for potential App Studio issues.
Implementing session cleanup and filter sync handlers (Gemini suggestion).
Despite these efforts, the problem persists.
Has anyone else experienced this discrepancy between App Studio and dashboards when using the domo.filterContainer()
API? Are there any known workarounds or best practices to ensure that clearing filters in the UI consistently clears the underlying data in App Studio apps?
Any insights or suggestions would be greatly appreciated!
Answers
-
Hi @Saaisathish,
We recently encountered similar behavior in one of our apps while using domo.onFiltersUpdate(). After failing to find a solution, we contacted the Domo Support team. I was informed that there were some related bugs that have since been fixed. You might want to reach out to Domo Support as well, it could be a similar issue.
If you found this post helpful, please use 💡/💖/👍/😊 below! If it solved your problem, don't forget to accept the answer.
1 -
Hey @Manasi_Panov thanks for your response, were you able to find a workaround to resolve this issue from the domo support or is it a bug specific to the instances that needs to be updated from their end?
0 -
Hi @Saaisathish,
The bug was related to something on their end. We just received a message that they fixed it without the need to change the app.
If you found this post helpful, please use 💡/💖/👍/😊 below! If it solved your problem, don't forget to accept the answer.
0
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 307 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 112 SQL DataFlows
- 649 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 790 Beast Mode
- 78 App Studio
- 43 Variables
- 746 Automate
- 187 Apps
- 475 APIs & Domo Developer
- 68 Workflows
- 16 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 406 Distribute
- 117 Domo Everywhere
- 279 Scheduled Reports
- 10 Software Integrations
- 139 Manage
- 136 Governance & Security
- 8 Domo Community Gallery
- 47 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive