Mega-Ultron-Super-Duper Connected Dataset to rule them all
BLUF: Should I join/append all of our data so we have one workable dataset?
This isn't a technical question, but rather theoretical. We've got data in many places (I'm sure this is common):
Budget in XYZ
Financials in ABC
Stats in DEF
Stats Historical (just switch systems so have a different datamart) in LMN
Everything that our end users do is taking pieces of each of these. I.e. How did we do this year (Stats) compared to last year (Stats Historical), and did that meet our expectations (Budget)? Is Revenue (Financials) in line with forcast (Budget)?
As it stands, we have to go to 4 different places to piece together the full story. My goal/hope/(maybe) pipe dream is to have all 4 sources of truth in one spot so these answers can be found simpler and more quickly.
What is the community's thoughts? Is this worth the time of development/implementation, or is it just "how things are"? Should I press into this as an initiative, or accept where we are at?
Any input is appreciated - I appreciate this community!
✅Did this solve your problem? Accept it as a solution!
❤️Did you love this answer? Mark it as "Awesome"!
👍Do you agree with this process? Click "Agree"!
Best Answer
-
@Data_Devon I would suggest going the append route for this data and adding a Category column to indicate the source of each row (Budget, Financials, etc.). Then you can use beast modes to present the output in a single card like this:
Budget Revenue:
sum(case when Category = 'Budget' then Revenue else 0 end)
Actual Revenue:
sum(case when Category = 'Financials' then Revenue else 0 end)
Variance:
sum(case when Category = 'Financials' then Revenue else 0 end) -
sum(case when Category = 'Financials' then Revenue else 0 end)
You should also check out @GrantSmith's writeup about how to do period-over-period analysis, which may be helpful for this type of data:
2
Answers
-
@Data_Devon I would suggest going the append route for this data and adding a Category column to indicate the source of each row (Budget, Financials, etc.). Then you can use beast modes to present the output in a single card like this:
Budget Revenue:
sum(case when Category = 'Budget' then Revenue else 0 end)
Actual Revenue:
sum(case when Category = 'Financials' then Revenue else 0 end)
Variance:
sum(case when Category = 'Financials' then Revenue else 0 end) -
sum(case when Category = 'Financials' then Revenue else 0 end)
You should also check out @GrantSmith's writeup about how to do period-over-period analysis, which may be helpful for this type of data:
2
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 102 SQL DataFlows
- 626 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 753 Beast Mode
- 61 App Studio
- 41 Variables
- 692 Automate
- 177 Apps
- 456 APIs & Domo Developer
- 49 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 398 Distribute
- 115 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 11 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 110 Community Announcements
- 4.8K Archive