Beast mode referencing

Hello,
I wonder why this won't work.
I get that the CASE WHEN can't have MAX() within it, but I thought by referencing the beast mode that uses the MAX() would process it as a subquery that references the output value instead of the formula MAX().
If this wouldn't work, is there an alternative to this? I needed the latest_unsent_campaign_acct to be dynamic that's why I brought it to the card before wrapping it with MAX()
Answers
-
it’s because you have an aggregate inside an aggregate which isn’t allowed. You could attempt to use a window function so the max is returned for each row depending on your partitions and then do the count on that value
COUNT(CASE WHEN `campaign_id` > MAX(`latest_unsent_campaign_acct`) FIXED (BY `your_partition_field_or_remove_by_clause`) THEN `campaign_id` END)
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**0 -
Hi @GrantSmith
Thanks. I tried but it doesn't work either. The use of partition was actually my initial approach, but I used MAX(MAX() FIXED (BY)) following the documentation on FIXED function. Neither of them worked.
It turns out, even the partition can't be within an aggregation as it works if I removed the COUNT()
0
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 307 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 112 SQL DataFlows
- 649 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 790 Beast Mode
- 78 App Studio
- 43 Variables
- 746 Automate
- 187 Apps
- 475 APIs & Domo Developer
- 68 Workflows
- 16 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 406 Distribute
- 117 Domo Everywhere
- 279 Scheduled Reports
- 10 Software Integrations
- 139 Manage
- 136 Governance & Security
- 8 Domo Community Gallery
- 47 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive