Hi
I seem to be seeing what looks like caching using Direct Query. Now I know how to direct query works and that every interaction with a visual sends a query to the underlying data source. What seems to be happening in the pilot we have developed (both in the service and desktop) is once all the options of any slicers have been selected once, any delay (and we get a delay) in refreshing visuals disappears.
For example;
We have a table with sale fact information and some DAX measures we also have a slicer with product dimension info slicing the fact table. When we first select a slicer value we see a delay in the fact table updating (refresh circle top left of the visual) this behaviour repeats the first time we select all the other options in the slicer. On any subsequent selections of the slicer options the fact table visual updates instantaneously. I can only think that data is being cashed which goes against all the documentation I have read about direct query.
Has anyone else exhibited this behaviour?
