Total Row on a tale card is giving incorrect values
The % you see in the final column is calculated as sum "column 6"/ sum "column 1". So in this case it should have been 14/17 but I get an incorrect answer. This is because the 17 you see is after the duplicates were removed( which is what I need to see) but to calculate the value in the last column it still considers the duplicates present in the first column.
Please let me know how to proceed. Thank you.
Best Answer

Hi @Saketh, so the total row for the card is calculated after the beast mode is calculated, meaning what you see happen is it’s adding your percentages instead of calculating your total percentage.
To go about getting a true total row, you'll need to use an ETL to group your data together and sum all your columns using a Group By tile, then using an Add Constant tile, put the value of Total in your label field, and then append this row to your original dataset.
11
Answers

Hi @Saketh, so the total row for the card is calculated after the beast mode is calculated, meaning what you see happen is it’s adding your percentages instead of calculating your total percentage.
To go about getting a true total row, you'll need to use an ETL to group your data together and sum all your columns using a Group By tile, then using an Add Constant tile, put the value of Total in your label field, and then append this row to your original dataset.
11 
Thank you for your prompt response @amehdad . So just to clarify the total row doesn't consider the beast mode formula but instead, just considers the same column and gives us the total avg percentage? i.e its adding bunch of %'s that precede the total row and gives me the final value instead of calculating column6/ column 1 like it did for every other row?
If that is indeed right  then how come the value shown in the first column avoids the duplicates? shouldn't it simply show the final number by adding all the previous values ?
Thank you for your help, much appreciated.
0 
It does consider the beast mode calculations but beast modes are calculated on a row by row basis whereas you need the beast mode to calculate using the full sum values of column 1 and 6. Which is why some prep work is needed on your dataset to ensure your data coming into the card is totalled so that the grand total row appears as expected.
4
Categories
 All Categories
 1.7K Product Ideas
 1.7K Ideas Exchange
 1.5K Connect
 1.2K Connectors
 292 Workbench
 4 Cloud Amplifier
 8 Federated
 2.8K Transform
 95 SQL DataFlows
 600 Datasets
 2.1K Magic ETL
 3.7K Visualize
 2.4K Charting
 685 Beast Mode
 43 App Studio
 38 Variables
 655 Automate
 170 Apps
 438 APIs & Domo Developer
 42 Workflows
 5 DomoAI
 32 Predict
 12 Jupyter Workspaces
 20 R & Python Tiles
 383 Distribute
 110 Domo Everywhere
 267 Scheduled Reports
 6 Software Integrations
 111 Manage
 108 Governance & Security
 8 Domo University
 25 Product Releases
 Community Forums
 39 Getting Started
 29 Community Member Introductions
 98 Community Announcements
 Domo Community Gallery
 4.8K Archive