Filtering is not supported Error
Hi,
I built a Radio Button selector card as a filter for 2 other cards. The 2 other cards are based off of 2 different datasets. The filter allows to filter for degree vs. no degree and the other 2 cards : one has information about average life expectation and the other average earnings.
I created the degree field in all 3 cards in a beast mode, but when I try to select in the filter either degree or no degree I get the following error: Filtering Degree is not supported. Consider sharing the card beast mode to the dataset.
Whe I try to share it, it tells me the following error: Rename Beat Modes to avoid conflict: Column already exist
So first of all it is not possible to share the beast mode and in the case it would be possible, I would have to rename the beast mode - but that would mean that the filter button would not affect the card where the beast mode got renamed. Correct? Any idea why I get the error messages and what I can do??
Comments
-
weird things can happen when you copy cards that contain beastmodes.
keep in mind a beast mode saved to a card is only accessible in the card.
if you have card 1 and it contains a beast mode called "test" saved to the CARD.
then you create card 2 which contains a beast mode called "test" saved to the DATASET.
THEN you tace card 1 and try to save your beast mode "test" to the dataset and you get your conflict. If you DELETE "test" from card 1, you won't necessarily instantly see "test" from card 2.
so before you delete anything, renamce card 1 "test" to "delete - test". then save and refresh the card and confirm that you see a beast mode "test" (saved to the dataset). NOW you can delete "delete-test" and replace it with "test" ... and proceed from there.
Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0 -
Last I checked, the filter interaction is not supported for Beast Modes even if it's saved to the dataset. I would suggest hard-coding the degree field into both of your datasets via an ETL.
As for the "Rename Beast Modes" error, I've been noticing that show up erroneously on cards recently so I would not worry too much about that. I've still been able to save my cards with the beast modes in them, although I'm not sure why the error keeps popping up.
0 -
you can't filter on AGGREGATE FUNCTIONS (like SUM() or COUNT()) in beast modes without a feature switch.
you can filter on non aggregate functions like CASE or IFNULL.
Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0 -
@jaeW_at_Onyx How do you turn on the feature switch?
0 -
@daniellecroft contact your CSM or support@domo.com. the feature you're asking for is "filter on aggregates in analyzer"
Jae Wilson
Check out my 🎥 Domo Training YouTube Channel 👨💻
**Say "Thanks" by clicking the ❤️ in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 102 SQL DataFlows
- 626 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 753 Beast Mode
- 61 App Studio
- 41 Variables
- 692 Automate
- 177 Apps
- 456 APIs & Domo Developer
- 49 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 398 Distribute
- 115 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 11 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 110 Community Announcements
- 4.8K Archive