Forum Discussion
How do I prevent caching data for each filter used in DirectQuery?
If you need 100% fresh data then you should modify your query by adding a random, meaningless filter.
Let's say you know value A is never more than 50. Add a filter for A<100+RAND().
Hi!
Found it, and I tried to set cache size to 0 (despite the warning in the system) to force system to make a new DirectQuery select each time, but it it became impossible to Refresh any data "maximum cahce size exceeded".
I did not found a feature for "clear cache older than x seconds" (for me 0 seconds :)), is there?
Maybe we must live with this: If one need 100% fresh data, one must use Refresh button? A user can of course not remember if a certain filter has been used (on now cached) since opened the report.
Super UserIf you need 100% fresh data then you should modify your query by adding a random, meaningless filter.
Let's say you know value A is never more than 50. Add a filter for A<100+RAND().
I faced same issue reported on top and tried your suggestion -- it doesn't work. Problem is, even when you add functions in your table's underlying query it still runs same query every time -- when query gets executed is when that random number is generated. However, from powerbi's perspective, query string hasn't changed.
We need more of a solution that will change the query every time it is CALLED, not when it executes.
