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
- 10.5K All Categories
- 3 Connect
- 913 Connectors
- 250 Workbench
- 458 Transform
- 1.7K Magic ETL
- 69 SQL DataFlows
- 476 Datasets
- 182 Visualize
- 249 Beast Mode
- 2.1K Charting
- 11 Variables
- 16 Automate
- 354 APIs & Domo Developer
- 88 Apps
- 3 Workflows
- 20 Predict
- 5 Jupyter Workspaces
- 15 R & Python Tiles
- 245 Distribute
- 62 Domo Everywhere
- 242 Scheduled Reports
- 20 Manage
- 41 Governance & Security
- 168 Product Ideas
- 1.2K Ideas Exchange
- 9 Community Forums
- 27 Getting Started
- 14 Community Member Introductions
- 55 Community News
- 4.5K Archive