Finding the "Growth Rate" of a metric in Beastmode
We are currently building a dashboard where looking at change over time is critical - ideally how we'd like to accomplish this is by measuring the growth rate, or change in the metrics over the period set by the analyzer.
Is it possible to calculate this in a beastmode while still retaining the ability to change the filters and time frames observed?
For example if the page analyzer was set to Q1 2017 and we were measuring weekly sales we'd want to see:
(last week of Q1 - first week of Q1)/first week of Q1
Sure we could calculate these in an ETL before it gets to the dataset but then we would lose our ability to determine what time period we want to look at, what granularity we want to see, and what other filters we can apply.
Best Answer
-
Austin, generically speaking, would your calculation look like this?
(last week of [page analyzer time period] - first week of [page analyzer time period] ) / first week of [page analyzer time period]
Beast mode query language allows you to pretty much only dynamically reference current_date, not the dates underlying the analyzer/date picker. That would be a very powerful feature, though. Definitely throw that one up in the ideas exchange board.
FWIW, I once helped build a custom app that generated a calculation like this. It had user input of two custom time ranges, and the app calculated the growth rate for a whole series of metrics based on the input. It was a pretty simple JS app and sat on a Domo page just like any other card. If you have a developer on staff it wouldn't take long to spin up something like that.
Aaron
MajorDomo @ Merit Medical
**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
Answers
-
Austin, generically speaking, would your calculation look like this?
(last week of [page analyzer time period] - first week of [page analyzer time period] ) / first week of [page analyzer time period]
Beast mode query language allows you to pretty much only dynamically reference current_date, not the dates underlying the analyzer/date picker. That would be a very powerful feature, though. Definitely throw that one up in the ideas exchange board.
FWIW, I once helped build a custom app that generated a calculation like this. It had user input of two custom time ranges, and the app calculated the growth rate for a whole series of metrics based on the input. It was a pretty simple JS app and sat on a Domo page just like any other card. If you have a developer on staff it wouldn't take long to spin up something like that.
Aaron
MajorDomo @ Merit Medical
**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 -
Yea! That's exactly what it would be - although instead of referencing the analyzer itself it could be accomplished by allowing for table level calculations in beastmodes similar to windowed calculations for Tableau.
This has been suggested in idea here - unfortunately it seems to have lost steam.
I've looked into building a JS app for this but we have a lot of concerns around mixing the functionality of custom cards and out of the box cards on pages that will face our external clients. We don't want them to get confused as to what filters they have applied where, why they can export from some cards and not others, etc.
Thanks,
Austin
0 -
Domo is working on window functions in beast mode, so I think you'll be able to see some of those this year (my guess). I look forward to some of this higher level analytical functionality.
Aaron
MajorDomo @ Merit Medical
**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 -
Oooh that is really useful knowledge!
Thanks for the info Aaron.
1 -
Are they finished with window functions yet? there are many use cases for this.
* CAGR
* Filtering to show only top 10 categories during a given (variable) period
etc.
etc.
0 -
Yes and no. There are some window functions available, but it's not officially supported according to Support. So you might have what you need, but you're on your own to make it work.
Try the documentation here.
Aaron
MajorDomo @ Merit Medical
**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"2
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