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
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 295 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 97 SQL DataFlows
- 608 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.4K Charting
- 710 Beast Mode
- 50 App Studio
- 39 Variables
- 668 Automate
- 170 Apps
- 446 APIs & Domo Developer
- 45 Workflows
- 7 DomoAI
- 33 Predict
- 13 Jupyter Workspaces
- 20 R & Python Tiles
- 391 Distribute
- 111 Domo Everywhere
- 274 Scheduled Reports
- 6 Software Integrations
- 116 Manage
- 113 Governance & Security
- Domo Community Gallery
- 31 Product Releases
- 9 Domo University
- 5.3K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 103 Community Announcements
- 4.8K Archive