expected beast mode behavior?
Comments
-
Yes. this is normal behavior.
I assume by two choices you mean either
sum(1)
OR
1
In Analyzer the default aggregation is sum. if you change the aggregation method on the second beast mode to AVG, MIN or MAX, you should see a different value.
if you have a beast mode with a built in aggregate, you cannot change the aggregation method to something else.
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 -
So whether I use 1 or sun it shows up as 179. Any other insights out there as to why?
0 -
"if you change the aggregation method on the second beast mode to AVG, MIN or MAX, you should see a different value."
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 -
got it- using an alternate aggregation does make it render correctly. and I figured out that the sum of 1 aggregating across the number of records in the test dataset did come out to 179. mystery solved, thank you.
0
Categories
- All Categories
- Product Ideas
- 2K Ideas Exchange
- Connect
- 1.3K Connectors
- 308 Workbench
- 7 Cloud Amplifier
- 10 Federated
- Transform
- 661 Datasets
- 117 SQL DataFlows
- 2.2K Magic ETL
- 819 Beast Mode
- Visualize
- 2.6K Charting
- 85 App Studio
- 46 Variables
- Automate
- 193 Apps
- 483 APIs & Domo Developer
- 85 Workflows
- 23 Code Engine
- AI and Machine Learning
- 22 AI Chat
- 3 AI Projects and Models
- 18 Jupyter Workspaces
- Distribute
- 116 Domo Everywhere
- 282 Scheduled Reports
- 11 Software Integrations
- Manage
- 142 Governance & Security
- 9 Domo Community Gallery
- 49 Product Releases
- 13 Domo University
- Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 115 Community Announcements
- 5K Archive