Create bar chart summing multiple columns/categories
I am new to Domo. So please bear with me.
If I have a dataset such as this.
I would like to end up with a bar chart such as the one I have (badly) drawn below. Where the "TRUE" values are counted along the y-axis. My problem is that I am unable to figure out a way to get three columns to show on the x-axis. (I know that this can be done rather indirectly by collapsing the columns, but I feel that there has to be a much simpler solution).
Thanks
Best Answer
-
... "the best way" ... please appreciate that i'm operating off of a napking drawing :P.
if it were me, yes, this is how i would structure the data. i might try to find shortcuts like excluding outputting rows where subscribed = false. but with the information available, yes, I believe normalizing the data is the better method for storing it.
now you might try to collapse the data before it arrives at Domo depending on etl constraints like how frequently the data updates, and acceptable latency, but that's a pipeline optimization question not a data modeling question.
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"1
Answers
-
While you may be able to hack your way to a solution, the best answer would be to reshape your data.
Use MagicETL and the Unpivot / Collapse Columns transform to collapse your data into 3 columns (ID, Subscription Name, and isSubscribed).
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"1 -
Thanks for you answer.
But the dataset has almost a million entries and around 65 of such columns. Collapsing the columns thus would result in 65 million rows. Would this still be the best way to do it?
0 -
... "the best way" ... please appreciate that i'm operating off of a napking drawing :P.
if it were me, yes, this is how i would structure the data. i might try to find shortcuts like excluding outputting rows where subscribed = false. but with the information available, yes, I believe normalizing the data is the better method for storing it.
now you might try to collapse the data before it arrives at Domo depending on etl constraints like how frequently the data updates, and acceptable latency, but that's a pipeline optimization question not a data modeling question.
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"1 -
If the napkin drawing works then it works ?
Thanks for the input.
0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 738 Beast Mode
- 57 App Studio
- 40 Variables
- 685 Automate
- 176 Apps
- 452 APIs & Domo Developer
- 47 Workflows
- 10 DomoAI
- 36 Predict
- 15 Jupyter Workspaces
- 21 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 124 Manage
- 121 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive