Why have the dates changed?
So I have put together a multi data source dashboard for our company. Yesterday, before everything ran overnight, all of the years worth of data was showing up. This morning, without changing any filters, the graphs are only showing about 15 years worth of data.
My instinct said that somehow the update caused to data to go missing but I see the earlier dates in the data in analyzer.
Is there a fix for this without having to recreate each card? (I still cant get all the way back to 1977 even when I recreate the card but it does go back further.)
Any insight would be helpful. Again no filters were applied and when I enter into analyzer, the date range still says 1977 to 2022
If this helps, feel free to agree, accept or awesome it!
Best Answer
-
@damen I have run into issues where I have a lot of historical data and if the date range filter is set to graph by year, it does not go all the way back. Support once told me that it has to do with their calendar system behind the scenes.
I was able to get around it by creating a beast mode that extracts the year from the date field that is on the x-axis and then put that beast mode field on the x-axis. The beast mode is simply YEAR(`datefield`) . See if that works for you.
**Check out my Domo Tips & Tricks Videos
**Make sure to any users posts that helped you.
**Please mark as accepted the ones who solved your issue.2
Answers
-
@MichelleH Yes. Most of the source data comes from databases that aren't rewritten but appended. The earliest dates from all sources in this dataflow are like this and have not been overwritten.
If this helps, feel free to agree, accept or awesome it!
0 -
@MichelleH So the 2nd screen shot is showing that the dates are available in analyzer. That view if of the 'data' table while in analyzer. The problem is the card isn't showing all the available data.
Here is a different view but basically showing the same thing that was mentioned by the previous post/pictures.
This is the same instance of analyzer.
If this helps, feel free to agree, accept or awesome it!
0 -
@RobSomers Its just a regular column. We aggregated it on average purchase price by year.
I just went through and removed all aggregates and changed from ave to all the other ones and the same issue is coming up.
If this helps, feel free to agree, accept or awesome it!
0 -
@damen I have run into issues where I have a lot of historical data and if the date range filter is set to graph by year, it does not go all the way back. Support once told me that it has to do with their calendar system behind the scenes.
I was able to get around it by creating a beast mode that extracts the year from the date field that is on the x-axis and then put that beast mode field on the x-axis. The beast mode is simply YEAR(`datefield`) . See if that works for you.
**Check out my Domo Tips & Tricks Videos
**Make sure to any users posts that helped you.
**Please mark as accepted the ones who solved your issue.2 -
@MarkSnodgrass Awesome. Yeah. That worked. Thank you.
If this helps, feel free to agree, accept or awesome it!
0
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 294 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 97 SQL DataFlows
- 607 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.4K Charting
- 707 Beast Mode
- 49 App Studio
- 39 Variables
- 667 Automate
- 170 Apps
- 446 APIs & Domo Developer
- 44 Workflows
- 7 DomoAI
- 33 Predict
- 13 Jupyter Workspaces
- 20 R & Python Tiles
- 391 Distribute
- 111 Domo Everywhere
- 274 Scheduled Reports
- 6 Software Integrations
- 115 Manage
- 112 Governance & Security
- Domo Community Gallery
- 31 Product Releases
- 9 Domo University
- 5.3K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 103 Community Announcements
- 4.8K Archive