Allow API searching for dashboards by any data source used within it (filter or widget), and/or allow searching for widgets that use a provided data source across all dashboards (without providing a dashboardId) | Product Feedback Forum

Chris Wallingford · 2026-05-31T18:52:13.678247Z

When we alter our data models with a breaking change, we don't want our clients' bespoke dashboards to break if we can avoid it. We have historically addressed this through an automated process that takes a "schema change" JSON file, and searches through dashboards for use of any "old schema" source/table/columns, updates then to the "new schema" source/table/column, and then imports the dashboard back into the system. This has worked well, but as time goes by, the process is taking longer and longer... due to there being so many more dashboards to investigate.We would like to limit our dashboard search to only dashboards that use a given data source. This is somewhat possible now in that the admin/search allows providing a data source name to filter results, but this filters only based on the primary data source in the dashboard, and would not return dashboards for the provided source where that source was not the primary data source on the dashboard. Were we able to search on primary and non-primary data sources, we could limit our dashboard search to only the sources that have schema changes.Alternatively, or in addition, we could accomplish something similar by scouring widgets instead of dashboards, updating only the widgets that use the provided data source, and posting them back to the environment. However, the widgets endpoint requires that a dashboardId be provided, see issue above.

MoreDiscussions

Allow API searching for dashboards by any data source used within it (filter or widget), and/or allow searching for widgets that use a provided data source across all dashboards (without providing a dashboardId) | Product Feedback Forum | Sisense Community