Hi @will.marriott ,
We also desperately need this. The static date ranges on a custom are very restrictive, having them dynamic would remove a large amount of headaches for us. I would say the dashboard reporting the business use is around 70% custom reports where they want to change the date, so having this associated to the dashboard that it is a relative reference to current date range would be a dream come true.
Examples of custom reports we have:
As you can see the above custom report is using the financial statements database to derive the layout the management require. This uses a custom period type of “Fiscal year to date (exclude current month)”. This works well for the current month, if however the user wants to look at last month, changing the date range on the dashboard does not impact the custom widget. Also, the solution of using custom period types has its own headaches…
Fiscal year to date (exclude current month) / Calendar year to date (exclude current month) defined periods
I have this set up as a defined period, only problem is if you look at the Fiscal YTD: This uses offsets, the date range logic is Sept (Most Recent) to Offset -1, this works for Feb to Dec, but in January no reports work as the logic would become Sept (Most Recent) to Aug prior year = 0 rows.
Having the date ranges compatible with the dashboard date range would remove a lot of custom period types, provide users the ability to use the one dashboard to traverse different time periods and crucially speed up build time of our databases as we could remove a lot of workaround “Period Types” we have to aggregate against on the DB (estimate a 40 minute reduction in build time).
Hope this makes sense and helps define the requirement at a nuts and bolts level.