Pivot Table summary values
Hi all, I'm very confused about what is going on with my pivot table.
The row&column totals are correct but the underlying cell values within the table are only showing a value from one part of the sum instead of the entire sum? What's worse, when I drill down, it shows the correct sum
Tried moving to a Mega Table and the readability is just not the same.
My next guess was to create a rollup dataset and nix the drill down capability altogether
Appreciate you all
Answers
-
Thanks friends!@Ashleigh I'm sorting on a beast mode but doesn't look like it removing it made much difference :(
@RobSomers It is pretty large... the dataset has 5.5M. When I apply filters to the pivot table card, it brings it down to about 10k. Do filters not help with "reducing the size"? What's weird is that it was working until I added a beast mode to filter out parts of the dataset
For context, the use case is to look at snapshots of a SFDC object on any given day. Ideally, we can view the trend in a bar/line chart and use a pivot table to see the $ breakout and drill down to which deals were forecasted on which date
0 -
Could you post your beast mode that you're using as a filter?
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**
0 -
A colleague recommended I move the transform to MagicETL so it's a formula card now instead of a beast mode.
The transform is a bit confidential so can't really share the exact statement. In essence, it adds a column to pull through existing $ value for each record depending on 3/4 sets of criteria
0 -
Could you post it with the columns and values used replaced with other names and values, so we can just see what the formula looks like? What the actual columns/values are shouldn't matter.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**
0 -
Hopefully this is enough?
CASE WHEN `Stage`='7'
THEN $
WHEN `Record Type` IN ('A','B')
AND `Stage` NOT LIKE '%7%'
AND `Score`>= #
AND DATEDIFF(`Snapshot Date`,`Last Modified Date`)<= #
THEN `$`
WHEN `Record Type` IN ('A','B')
AND `Score` IS NULL
AND `Stage` NOT LIKE '%7%'
AND ((`Stage`='1' AND `Days in Current Stage`<=#) OR
(`Stage`='2' AND `Days in Current Stage`<=#) OR
(`Stage`='3' AND `Days in Current Stage`<=#) OR
(`Stage`='4' AND `Days in Current Stage`<=#) OR
(`Stage`='5' AND `Days in Current Stage`<=#) OR
(`Stage`='6' AND `Days in Current Stage`<=#))
THEN `$`
WHEN `Record Type` IN ('C','D')
AND `Score`>#
AND `Stage` NOT LIKE '%7%'
THEN `$`*#
WHEN `Record Type` IN ('C','D')
AND `Score`<=# AND `Score`>#
AND `Stage` NOT LIKE '%7%'
THEN `$`*#
WHEN `Record Type` IN ('C','D')
AND `Score`<=50 OR `Score` IS NULL
AND `Stage` NOT LIKE '%7%'
THEN `$`*#
END
0 -
I would put ELSE 'Unknown' right before the end to more easily identify cases where none of your rows meet them conditions and see if there's anything that should have a value but doesn't. Then you can see if that has anything to do with what's missing.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**
3
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 299 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 729 Beast Mode
- 54 App Studio
- 40 Variables
- 680 Automate
- 175 Apps
- 451 APIs & Domo Developer
- 46 Workflows
- 8 DomoAI
- 34 Predict
- 14 Jupyter Workspaces
- 20 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 121 Manage
- 118 Governance & Security
- Domo Community Gallery
- 33 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive