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.4K Product Ideas
- 1.4K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 278 Workbench
- 4 Cloud Amplifier
- 4 Federated
- 2.7K Transform
- 89 SQL DataFlows
- 557 Datasets
- 2K Magic ETL
- 3.3K Visualize
- 2.3K Charting
- 571 Beast Mode
- 11 App Studio
- 28 Variables
- 579 Automate
- 141 Apps
- 414 APIs & Domo Developer
- 23 Workflows
- 1 DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 352 Distribute
- 92 Domo Everywhere
- 258 Scheduled Reports
- 2 Software Integrations
- 92 Manage
- 89 Governance & Security
- 9 Product Release Questions
- Community Forums
- 42 Getting Started
- 28 Community Member Introductions
- 88 Community Announcements
- 4.8K Archive