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.2K Product Ideas
- 1.2K Ideas Exchange
- 1.3K Connect
- 1.1K Connectors
- 273 Workbench
- Cloud Amplifier
- 3 Federated
- 2.7K Transform
- 78 SQL DataFlows
- 524 Datasets
- 2.1K Magic ETL
- 2.9K Visualize
- 2.2K Charting
- 433 Beast Mode
- 22 Variables
- 510 Automate
- 114 Apps
- 388 APIs & Domo Developer
- 8 Workflows
- 26 Predict
- 10 Jupyter Workspaces
- 16 R & Python Tiles
- 331 Distribute
- 76 Domo Everywhere
- 255 Scheduled Reports
- 65 Manage
- 65 Governance & Security
- 1 Product Release Questions
- Community Forums
- 40 Getting Started
- 26 Community Member Introductions
- 67 Community Announcements
- 4.8K Archive