We created saved reports that have been scheduled to run over night (Range=Last 24 hours). These saved reports are utilized by dashboards through base searches.
We want to be able to change the time range of the report in the dashboard so its not always displaying the results gathered in the last 24 hours. Right now, whenever we changed the time picker in the dashboard, the results stay the same.
You can do that, but unless you carefully control it, you are going to cause yourself many headaches if you go down that route.
Basically, if you keep the dashboard based on a saved report, there is very little load on the indexers. If you allow the users to wander off the saved report, then you are running new searches for real. How many users do you want doing that?
The most obvious architecture to get you where you want to go is to have dropdowns that allow the user to select the base search, which could be any of a limited range of saved searches that you have devised and scheduled.
That's not tough to do, and once you learn how to do it it doesn't require a lot of maintenance, except when you add or remove options. Here's one example...
If you stick to a single savedsearch, and just give them a choice to select prior versions of it, then you can have the base search using loadjob with artifact_offset=N (where N is however many prior generations back you want).