a beast mode that calculate revenues from diff sources
Hi Everyone,
I have a data set that shows where our tickets are being created and revenue.
And I created 2 beast modes that separate where our tickets are being generated -
CASE WHEN Source
= 'G360' THEN 0 ELSE 1 END
and
CASE WHEN Source
= 'G360' AND (Board_Name
='Field Services - MAC' or Board_Name
='Field Services - Repair') THEN 1 ELSE 0 END
Now I want to add a revenue column to each of the beast mode that was created but i'm having issues creating a beast mode.
We have a calculation measurement that we show the total revenue for an account.
What beast mode function would I use to show the revenue for each of the beast mode?
Would I add on to the beast mode that was created by adding the calculation measurement?
Any assistance is greatly appreciated.
Best Answers
-
I understand now.
The data will need to be pivoted in magic ETL to achieve the desired effect.
To confirm, do you want to see a table in the following format as your output?
0
Answers
-
Hi @MichelleH, please see below.
Basically, I want the Revenue to show for each source- Non -G360, Non-360-FS, and G360-FS.
These show how many tickets are created for each and the revenue total it produces for the # of tickets. We do have a measurement for the Total revenue but we want it separated from each source. Hopefully it makes sense. Thank you again for the assistance.
0 -
hi @MichelleH , any thoughts on what beast mode calc can be created to provide the data?
Thank you again for the assistance.
0 -
Hey Abe,
What is the meaning of the numbers in the Non-G360 column? Are those numbers an identifier?
If those numbers are an ID, do you want to see the sum of revenue for each ID?
Thanks,
0 -
hi @nmizzell, thank you for the assistance.
So those numbers represent how many tickets have been opened. The columns- non-g360, non-g360- fs, and g360-fs are sources on where are tickets are being created.
Non-G360 column shows 3 tickets have been created with a total revenue of $$$$ from those 3 tickets. And so forth with the other columns.
0 -
I understand now.
The data will need to be pivoted in magic ETL to achieve the desired effect.
To confirm, do you want to see a table in the following format as your output?
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
- 102 SQL DataFlows
- 626 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 755 Beast Mode
- 61 App Studio
- 41 Variables
- 693 Automate
- 178 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