Menu Item Order Rate
We are attempting to design a card that displays the order rate (Qty Sold/100 Guests) for different categories of menu item. My issue is that the traffic measure is duplicated for each item sold so the calculation works at the detail level but not always at the summary level (Category totals). We tried a sum(distinct) function but sometimes the traffic measure across dates is the same so this fails.
And here is a card I built to illustrate the issue:
https://pappas.domo.com/page/287596754/kpis/details/962548900
You can see that over the two days, traffic is the same so the actual Qty/HC should be 12.78 (79/618*100).
Best Answer
-
I will need to test this but it also gave me a another idea to test. If I create a key on the lowest level detail (date_revenuecenter_daypart) then I should be able to sum the traffic column and then divide by count(distinct key)
1
Answers
-
Good morning @cmarutzky, can you share a screenshot or upload an example of the dataset?
And how are you wanting to use the aggregations? Summary number? Data label?
cg
Domo Consultant
**Say "Thanks" by clicking the "heart" in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1 -
Not sure of the best way to show the data. This is a screen shot of the example card with the columns.
1 -
I'm not sure if it will work for your larger data set, but I was able to use this formula to get to your desired results with your sample data:
(sum(`Qty`) / sum(`Traffic (Sum)`)) * COUNT(DISTINCT `Date`)
“There is a superhero in all of us, we just need the courage to put on the cape.” -Superman1 -
If what @ST_-Superman-_ posted doesn't work, then I am happy to dig a little deeper.
And sorry @cmarutzky for the delay in response, it looks like my last correspondence didn't post to the thread. But no excuses!
Which item is our category on this dataset? And what level of date granularity is ideal?
That is to say, as currently displayed in your png, we might be able to use some beastmodes to aggregate the data depending on which fields your users need to see.
This would probably be easier if I could access your instance, unfortunately I can't. So if you could just build a quick table of how you want the ideal card to look I can take a stab at some beastmode aggregations.
Domo Consultant
**Say "Thanks" by clicking the "heart" in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"1 -
I will need to test this but it also gave me a another idea to test. If I create a key on the lowest level detail (date_revenuecenter_daypart) then I should be able to sum the traffic column and then divide by count(distinct key)
1 -
#Math
Love it! Let us know how it goes
@cmarutzky wrote:I will need to test this but it also gave me a another idea to test. If I create a key on the lowest level detail (date_revenuecenter_daypart) then I should be able to sum the traffic column and then divide by count(distinct key)
Domo Consultant
**Say "Thanks" by clicking the "heart" in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"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