I have an unexpected outcome of a beast mode calculated column, can you help?
I've been working on a dashboard that has a radio selector to select which project the dashboard presents data from.
In this process, if an option is not set on the radio selector, my dashboard populates with "Please filter on Project" on most of my cards except one which is not behaving as expected.
For context, each project has a name, manager and sponsor; with my in-card filters, there are nine projects.
The code below works as intended
CASE WHEN COUNT(`Project_Manager`) = 1 THEN CONCAT('Delivery Lead: ',`Project_Manager`,' ', 'Accountable Executive: ', `Project_Sponsor`) ELSE 'Please Filter on Project' END
However, as soon as I add more to the Concat function, as you can see below.
CASE WHEN COUNT(`Project_Manager`) = 1 THEN CONCAT('Project Name: ',`Project_Name`,' ', 'Delivery Lead: ', `Project_Manager`,' ', 'Accountable Executive: ', `Project_Sponsor`) ELSE 'Please Filter on Project' END
CASE WHEN COUNT(`Project_Name`) = 1 THEN CONCAT('Project Name: ',`Project_Name`,' ', 'Delivery Lead: ', `Project_Manager`,' ', 'Accountable Executive: ', `Project_Sponsor`) ELSE 'Please Filter on Project' END
Both outputs do not behave as expected and populate with the first project of the nine instead of the 'Please Filter on Project' as intended, even though there are 9 Project_names/managers etc.
Any help with this would be greatly appreciated.
Hi @Stuck ,
Any way you can show the actual data or a mock up? It'd be good to see a screenshot of what these fields look like and your formula to the right in a table to gain more context.
You're only one dashboard away.
Click here for more video solutions:1
Hi MichelleH, prior to filters, yes, after filters, no. The idea of the dashboard is that using a single select radio selector on the page users are able to reduce the number of projects to 1. With no filtering taking place it will return the "Please filter on Project". This criteria has worked on all other cards on my dashboard with no issue, but as soon as I add in that extra line of code it breaks down and stops working for just this card.0
As for the data set - its mostly just as simple as project name, project manager and project sponsor. My solution is currently splitting out the "project Name" and all the other components into two cards, which works but doesn't look as tidy.0
@Stuck Case statements tend to get messy when mixing aggregates with row-level data, which is likely the cause of why that is not working. Have you tried wrapping a MAX() around your CONCAT() to artificially aggregate your one row? If that doesn't work then it sounds like you've found a decent work-around by splitting the data into multiple cards.1
- 10.5K All Categories
- 8 Connect
- 918 Connectors
- 250 Workbench
- 472 Transform
- 1.7K Magic ETL
- 69 SQL DataFlows
- 477 Datasets
- 198 Visualize
- 254 Beast Mode
- 2.1K Charting
- 11 Variables
- 82 Cards, Dashboards, Stories
- 17 Automate
- 354 APIs & Domo Developer
- 89 Apps
- 3 Workflows
- 20 Predict
- 5 Jupyter Workspaces
- 15 R & Python Tiles
- 247 Distribute
- 63 Domo Everywhere
- 243 Scheduled Reports
- 21 Manage
- 42 Governance & Security
- 178 Product Ideas
- 1.2K Ideas Exchange
- 12 Community Forums
- 27 Getting Started
- 14 Community Member Introductions
- 55 Community News
- 4.5K Archive