Time Intelligence in DOMO
Hello,
Is time intelligence possible through Beast Mode? Meaning is row level context possible - if the date on the current row is 1/1/2019 can a measure effectively be instructed to go back exactly one year and grab that value and insert it in the row? Attached is an example data set where I would want a PY measure.
I've tried to follow the exact instructions below from the URL below but have not had success. : https://knowledge.domo.com/Visualize/Adding_Cards_to_Domo/KPI_Cards/Transforming_Data_Using_Beast_Mode/Sample_Beast_Mode_Calculations%3A_Period-over-Period_Transforms#YOY:_Multi-Period_Comparison
In reading through the measures, I'm not seeing where logic is applied at the row level that would give DOMO context to go back a certain internval to grab the prior year amount.
Thanks in advance!
Best Answer
-
It's best in Domo (and really any system) to build transformations in the ETL, and reserve Beast Mode for those things you can't achieve because of dynamic analysis. I'd also caution against forcefitting solutions across tools. They will each have their own optimum ways to achieve results.
I find that many people I work with drastically overuse beast mode. I understand why, but you'll find more stable long-term solutions using ETL.
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"0
Answers
-
Hello - Have you tried achieving this in Magic ETL? There, you can created a column which is the date field minus one year, and then rejoin it to itself to pull in the prior year figure as its own field. Magic ETL handles loops well.
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"0 -
I have not tried it yet - I figured that was one route (sounds like the approach I will have to take). I was more just trying to explore whether the beast mode functions / the way DOMO is built if the measures have the capability of doing any type of time intelligence like you'd see in Tableu or Power BI.
Thank you
0 -
It's best in Domo (and really any system) to build transformations in the ETL, and reserve Beast Mode for those things you can't achieve because of dynamic analysis. I'd also caution against forcefitting solutions across tools. They will each have their own optimum ways to achieve results.
I find that many people I work with drastically overuse beast mode. I understand why, but you'll find more stable long-term solutions using ETL.
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"0 -
Thank you! Very helpful advice/thoughts on the subject.
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