Compare to Budget - Actuals in one Dataset and Budget Values in second Dataset
Hi community,
BLUF: How can I compare budget to actual?
We have data in one system that holds our actual sales amounts. We have data in a separate system that holds the budgeted sales amounts. I want to show the actuals and the budgeted in the same card.
This seems easy enough in theory, but I've been struggling to implement it. The biggest issue, of course, is that the two systems speak different languages. The Actual dataset has the location titled as "Location", where the Budget dataset has the location titled as "Subsidiary". Other examples of discrepancies: LastName, Last. Account, Stats Account.
If the column name was the only issue, then it'd be simple enough. But unfortunately the underlying data is different too. For instance, in Actual, the Location is listed as "Sioux Falls", but in Budget, the Location is listed as "100 Sioux Falls"
There isn't one column that's common across the two datasets, so I don't know how to join them. If I do ETLs to CASE WHEN one dataset into the other's language, that seems overly cumbersome for what seems to be a simple ask.
I've tried everything I can think of. I would love to see a bar that has the "budgeted" amount, and then a bar that has the "actual" amount.
Any help is appreciated.
✅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_Dev, I'm suggesting the opposite. If you take your monthly budget values, and turn them into daily budget values (by either dividing by the number of days in the month, or aggregating up to the year and dividing by the number of days in the year), you will end up with daily budget and daily actuals. This will let you do things like, MTD actual vs budget, last 30 days actual vs budget, etc. It will also let you filter to any date range, and have your actual vs budget be accurate. See here for a reference.
If you go through and map all the values, I would recommend doing this in a new column rather than updating the values in the existing column. This will let you display the data using the non-edited values, but still join.
David Cunningham
** Was this post helpful? Click Agree 😀, Like 👍️, or Awesome ❤️ below **
** Did this solve your problem? Accept it as a solution! ✔️**1
Answers
-
You'll need to do some mapping to create a way to join. I would also personally recommend aggregating up to a daily budget/actual amount in your ETL. You would then need to join to a date dimension table to fill in data for days where there were no "Actual" sales, but there was a budget. Together this will enable you to create a dynamic and filterable budget vs actual for any time period.
David Cunningham
** Was this post helpful? Click Agree 😀, Like 👍️, or Awesome ❤️ below **
** Did this solve your problem? Accept it as a solution! ✔️**2 -
Thanks David_Cunningham for a quick response!
So, to clarify, I'll need to remap all of the actual columns so that they match exactly how Budget columns are reported. This is what I was afraid of 😂
"Please expand upon your aggregating up to a daily budget/actual" comment. Our actuals are on a daily basis and our budget is on a monthly basis. Are you suggesting I combine all actuals to aggregate them up to a Monthly basis?
✅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"!
0 -
@Data_Dev, I'm suggesting the opposite. If you take your monthly budget values, and turn them into daily budget values (by either dividing by the number of days in the month, or aggregating up to the year and dividing by the number of days in the year), you will end up with daily budget and daily actuals. This will let you do things like, MTD actual vs budget, last 30 days actual vs budget, etc. It will also let you filter to any date range, and have your actual vs budget be accurate. See here for a reference.
If you go through and map all the values, I would recommend doing this in a new column rather than updating the values in the existing column. This will let you display the data using the non-edited values, but still join.
David Cunningham
** Was this post helpful? Click Agree 😀, Like 👍️, or Awesome ❤️ below **
** Did this solve your problem? Accept it as a solution! ✔️**1 -
That makes sense @david_cunningham. Thank you for your thorough explanation.
I see the quote of what must of been a previous question and response, but I don't see a link to the original post that your answer responded to. Perhaps that isn't important but wanted to be sure I wasn't missing something.
Thank you David!!
✅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"!
0 -
@Data_Dev - here is a link to the entire post.
David Cunningham
** Was this post helpful? Click Agree 😀, Like 👍️, or Awesome ❤️ below **
** Did this solve your problem? Accept it as a solution! ✔️**0 -
Resurrecting this….
@david_cunningham I still don't fully understand how to Cartesian Join on the date dimension table. I oversimplified our dataset, so the screenshots you provided couldn't translate directly to our data.
I want to join these two datasets to see how many appointments we have scheduled compared to how many we budgeted for the same time frame.
The difficulty increases because we have so many extra variables: different locations, different employees, different TYPES of appointments, etc.
I'm at a loss, but I still think this is possible. Let me know any thoughts!✅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"!
0
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
- 101 SQL DataFlows
- 622 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 748 Beast Mode
- 59 App Studio
- 41 Variables
- 686 Automate
- 176 Apps
- 453 APIs & Domo Developer
- 47 Workflows
- 10 DomoAI
- 36 Predict
- 15 Jupyter Workspaces
- 21 R & Python Tiles
- 396 Distribute
- 113 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 125 Manage
- 122 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 109 Community Announcements
- 4.8K Archive