Year over Year Cards

Question regarding year over year cards.
Currently I have a card that shows YTD vs Prior year and its working as expected
however if I change the dashboard filter to be last 12 months, the card seems to stop working
Since my "compare to" field in the card is set to "1 year ago" I was expecting that this card would be comparing 1 year ago to the last 12 months but thats obviously not what is happening in this card.
Is there any way to fix this ?
Best Answer
-
Hello @calvert_schaefer,
One approach, as suggested by John Le, involves using variables as a solution. However, is you want to compare Fiscal Years, this creates a huge challenge that requires a more complex Beast Mode formula.
Another viable solution is utilizing ETL processes to create a column, such as 'Sales_Last_FY', which can then be utilized alongside 'Sales' in your reports.
Let me know if you need additional explanation for both approaches.
If you found this post helpful, please use 💡/💖/👍/😊 below! If it solved your problem, don't forget to accept the answer.
1
Answers
-
Hi @calvert_schaefer ,
You could use variables to help you out instead of using the prebuilt compare to fields in the date dropdown. I made a video to show you:
https://www.loom.com/share/601578f4d58149aeabc5fcc1c6ac4bab?sid=36378d0e-22b0-4a88-bfcd-7a7d3569bc7a
John Le
Are you on my newsletter? If not, signup here so you don't miss out on my Domo tricks, alerts about my webinars, cooking tips and more
Signup here:
0 -
Hello @calvert_schaefer,
One approach, as suggested by John Le, involves using variables as a solution. However, is you want to compare Fiscal Years, this creates a huge challenge that requires a more complex Beast Mode formula.
Another viable solution is utilizing ETL processes to create a column, such as 'Sales_Last_FY', which can then be utilized alongside 'Sales' in your reports.
Let me know if you need additional explanation for both approaches.
If you found this post helpful, please use 💡/💖/👍/😊 below! If it solved your problem, don't forget to accept the answer.
1 -
@Manasi_Panov thanks for your context. Based on the variable video I believe if I want the card to interact with the date range filter on the dashboard the summary table is the best option. I was just hoping to avoid creating another table for something this simple.
My comparison is always PowerBI where I can just create a measure without any additional ETL/tables/etc
Sales_PY = calculate(sum('sales'),sameperiodlastyear('calendar'[date])
0
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 305 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 107 SQL DataFlows
- 648 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 775 Beast Mode
- 75 App Studio
- 43 Variables
- 734 Automate
- 186 Apps
- 471 APIs & Domo Developer
- 63 Workflows
- 14 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 403 Distribute
- 117 Domo Everywhere
- 277 Scheduled Reports
- 9 Software Integrations
- 137 Manage
- 134 Governance & Security
- 8 Domo Community Gallery
- 44 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive