Two Data Sets, Differently Named Fields - Unable to create paired filter for dashboard cards

Domo community - need a hand on this one.
I have two datasets:
a) Client records (note: uses client UNID of "SGId")
b) Events related to the Clients (note: uses client UNID of "ShowGroupID")
Both sets have a common UNID that identifies the clients. One is named SGId and the other ShowGroupID as noted above.
For the B data set, I set up a beast mode calc to rename the field to match (case sensitive) the field for A data set (screenshot below).
I then USED that Beast mode field in the card table on the dashboard (additional screenshot below).
I then joined/paired the filter on the Dashboard (additional screenshot below).
When I then use the filter on the dashboard for a specific Client SGId, I'm unable to find a known client SGId that exists in Dataset A but does NOT exist in Dataset B. This client did not have any events.
Question: How do I resolve this paired filter such that it will allow filtering on all SGId's regardless of whether the client record has no events? I would expect to be able to filter on such a client record and simply have the first table populate with a single row representing that client and then not display anything in the second card.
Thoughts on how to resolve this?
Thank you!!!
Screenshot of Beast Mode Calc Renaming Field in B Dataset
Using the new beast mode field in table configuration:
Paired Filter Screenshot
Answers
-
You should be able to filter on the beast mode if you're saved the beast mode to the dataset. Is it saved to the card only or to the dataset?
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**0 -
Grant - thanks for jumping in.
Yes, it has been saved to the dataset (screenshot below).
One thing I do notice is that when I go into the Dashboard and hit the "+" Filter to get the data field selection, when I scroll down to the SGId (client UNID), it has the arrow which is the indicates that Domo sees a matching field across both Datasets. When I click on it, the boxes are never checked for the pairing (despite the fact that I've already paired, saved, then saved the actual filter widget on the screen. Not sure if that means anything (second screenshot).
Lastly, given that the SGId that is not available for selection in the filter is also a Company that has NO events, could that be related to the issuer?
0 -
In my experience, the "pairing" doesn't really matter. It typically filters all DataSets regardless. I would try setting up a filter card, built on DataSet A, add it to the dashboard and see if that correctly filters.
Was this comment helpful? Click Agree or Like below.
Did this comment solve your problem? Accept it as the solution!0 -
Hello @afieweger
Thanks for reaching out to our community forum.
1. Use a Page-Level Filter (instead of a paired filter)
i. Add a page-level filter using the SGId field from Dataset A only.
ii. This allows the filter to recognize all SGIds, even if no corresponding record exists in Dataset B.
iii. Both cards will respond to the filter, but the second one will just return empty results for clients with no events.2. Use Magic ETL/View to Pre-Join Both Datasets
i. Create a left join of Dataset A to Dataset B using SGId = ShowGroupID.
ii. This ensures every client record is retained, even if there are no events.
iii. Build your cards off this joined dataset.
iv. Use standard filters (not paired) on this unified dataset.
If you still encounter an issue. I would suggest opening a support ticket. Our team will be happy to assist you further. When submitting the case, please include relevant details such as URL of dataset/account, screenshots of error. This information will help us understand the issue better and provide a timely solution.0
Categories
- All Categories
- 2K Product Ideas
- 2K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 311 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3.8K Transform
- 657 Datasets
- 115 SQL DataFlows
- 2.2K Magic ETL
- 815 Beast Mode
- 3.3K Visualize
- 2.5K Charting
- 81 App Studio
- 45 Variables
- 775 Automate
- 190 Apps
- 481 APIs & Domo Developer
- 81 Workflows
- 23 Code Engine
- 40 AI and Machine Learning
- 20 AI Chat
- 1 AI Playground
- 1 AI Projects and Models
- 18 Jupyter Workspaces
- 410 Distribute
- 120 Domo Everywhere
- 280 Scheduled Reports
- 10 Software Integrations
- 144 Manage
- 140 Governance & Security
- 8 Domo Community Gallery
- 48 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 114 Community Announcements
- 4.8K Archive