Currently, when mapping datasets to Filter Views in the Dashboard Filter View, Domo consistently prioritizes the dataset of the first card on the dashboard. If a user attempts to filter for an attribute that does not exist in the first card’s dataset—even if it does exist in the second or third card’s dataset—the filter returns no results or fails to apply correctly.
The Use Case
Consider a dashboard designed for order management:
- Card A (Top): A "Backlog Report" showing only Open Orders.
- Card B (Bottom): A "Shipment Report" showing Closed/Shipped Orders.
If a user searches for a specific Order Number (field in both datasets) that has already been closed, the filter fails to find it because it looks at the Backlog dataset first. Because the order is no longer in the backlog, it appears as though the data doesn't exist, even though it is present in the Shipment dataset right below it.
The Current (Suboptimal) Workaround
The current fix is to move the Shipment report to the top of the dashboard. However, this is not ideal from a logical reporting standpoint. The Backlog report is the primary driver of the business process and belongs at the top; we shouldn't have to compromise the visual hierarchy and "story" of a dashboard just to make the filtering logic function.
Proposed Solution
I propose a way to manually designate a Primary Mapping Dataset for filters, or a logic update where:
- The filter scans all mapped datasets for the value.
- Users can "rank" the priority of datasets in the Filter View settings, independent of the physical card layout on the page.
