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.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 737 Beast Mode
- 55 App Studio
- 40 Variables
- 684 Automate
- 176 Apps
- 452 APIs & Domo Developer
- 46 Workflows
- 10 DomoAI
- 35 Predict
- 14 Jupyter Workspaces
- 21 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 123 Manage
- 120 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive