Monthly Bookings vs Quota Chart
I am using data pulled from Salesforce, but I want to show the bookings per month compared to the goal per month (essentially a chart using a scale marker that changes)
The issue is that the goal is different every month. Is there a way to automatically build this in using Beastmode or a new DataFlow?
Best Answer
-
Hi
I would use and even simpler aproach
Using Shelly's tables, but relabling Month in the quota dataset to match the date on the main dataset
Main data set:
Transaction Id Close Date Amount
1 01/01/2019 25.00
2 01/15/2019 10.00
3 01/20/2019 25.00
4 02/01/2019 25.00
5 02/15/2019 10.00Goals data set (domo web form):
Close Date Goal Amount
01/31/2019 50.00
02/28/2019 40.00Simply append the two data set so that the new table looks like this:
Transaction Id Close Date Amount Goal Amount
1 01/01/2019 25.00
2 01/15/2019 10.00
3 01/20/2019 25.00
4 02/01/2019 25.00
5 02/15/2019 10.0001/31/2019 50.00
02/28/2019 40.00This will work exactly as you need it to. I use this set up myself for every Measure vs Budget type card/dataset.
I would even create the quota table with weekly or dailyquotas rather than monthly, you might get an even better insight than anticipated.
0
Answers
-
@TacoShelly - I think one of your solutions may work for this.DataMaven
Breaking Down Silos - Building Bridges
**Say "Thanks" by clicking a reaction in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1 -
Can you describe your data a bit more? Does it already contain your total bookings for the month and your goal for the month? Seems like you could very likely use a beast mode to try to get where you're going data wise.
As for the chart the Line + Stacked bar might work well, where the line is your goal for bookings and the bar shows actual bookings (as opposed to setting the goal manually within chart properties this'll allow the goal to be different each month.
0 -
@TacoShelly I have the bookings data coming from Salesforce but do not have the monthly quota number in Domo yet, not quite sure how to go about adding this (create a Domo online form, build it out in Beastmode)?
0 -
Ah I get it. Yeah I think using a Domo Online form (or whatever spreadsheet you're currently getting the goal data in) would work well. Then you can use a data flow to join the two. This'll make it easier to put new data in for future years/months.
Or you could also use a "case when" in beast mode to essentially say:
When date = January 2018 then goal is x
But that seems like a lot more work to maintain.
0 -
@TacoShelly I'm just not sure how to join the Domo form and the data together to show what I want to show...
0 -
All good I'm happy to try to help!
First, can you send me what colums exist in your SalesForce data that are pertinent to bookings?
We can use that to understand the granularity that you're starting from to try to get to your monthly bookings number. Is it individual transactions? Daily numbers? Monthly numbers?
Then once we've gotten your monthly booking number we'll know what you need in the goal so that you can match the two up in a data flow.
0 -
@TacoShelly They are individal transactions/opportunities. I will be using the close date and amount fields, so I would sum them on a monthly basis on the DOMO card. I would also somehow need to add the monthly goal number in there.
0 -
Perfect, so your data might look something like this:
Main data set:
Transaction Id Close Date Amount
1 01/01/2019 25.00
2 01/15/2019 10.00
3 01/20/2019 25.00
4 02/01/2019 25.00
5 02/15/2019 10.00Goals data set (domo web form):
Month Goal Amount
01/31/2019 50.00
02/28/2019 40.00Then you can use a Data Flow with each of those datasets as an input. In the Data Flow you can use the Close Date field and the Date Operators to create a field called Month that marks them each with a date that gives you the end of that month. At which point your main data set would look something like this:
Main data set:
Transaction Id Close Date Amount Month
1 01/01/2019 25.00 01/31/2019
2 01/15/2019 10.00 01/31/2019
3 01/20/2019 25.00 01/31/2019
4 02/01/2019 25.00 02/28/2019
5 02/15/2019 10.00 02/28/2019Then you can group the Main data set by Month, at which point your data would look something like this:
Main data set:
Amount Month
60.00 01/31/2019
35.00 02/28/2019the do a join with your Goals data set at which point your data would look something like this:
Joined data set:
Amount Month Month_1 Goal Amount
60.00 01/31/2019 01/31/2019 50.00
35.00 02/28/2019 02/28/2019 40.001 -
Hi
I would use and even simpler aproach
Using Shelly's tables, but relabling Month in the quota dataset to match the date on the main dataset
Main data set:
Transaction Id Close Date Amount
1 01/01/2019 25.00
2 01/15/2019 10.00
3 01/20/2019 25.00
4 02/01/2019 25.00
5 02/15/2019 10.00Goals data set (domo web form):
Close Date Goal Amount
01/31/2019 50.00
02/28/2019 40.00Simply append the two data set so that the new table looks like this:
Transaction Id Close Date Amount Goal Amount
1 01/01/2019 25.00
2 01/15/2019 10.00
3 01/20/2019 25.00
4 02/01/2019 25.00
5 02/15/2019 10.0001/31/2019 50.00
02/28/2019 40.00This will work exactly as you need it to. I use this set up myself for every Measure vs Budget type card/dataset.
I would even create the quota table with weekly or dailyquotas rather than monthly, you might get an even better insight than anticipated.
0 -
I would say what graph is up to you.
Maybe use Line + Bar
Date the x axis
Sum of Quota the line
Sum of Booking the bar
Alternatively, both as bar and the difference between the two as as line
0 -
When the transactions haven't happened yet i.e. Future Monthly Goals and Opportunities for those goals how would you go about displaying the future month goals if there are not Opportunities with dates to group by month?
0
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 293 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 97 SQL DataFlows
- 607 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.4K Charting
- 707 Beast Mode
- 49 App Studio
- 39 Variables
- 667 Automate
- 170 Apps
- 446 APIs & Domo Developer
- 44 Workflows
- 7 DomoAI
- 33 Predict
- 13 Jupyter Workspaces
- 20 R & Python Tiles
- 391 Distribute
- 111 Domo Everywhere
- 274 Scheduled Reports
- 6 Software Integrations
- 115 Manage
- 112 Governance & Security
- Domo Community Gallery
- 31 Product Releases
- 9 Domo University
- 5.3K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 103 Community Announcements
- 4.8K Archive