Forum Discussion
Direct Query Service : Slicer Does not update when a there is a change made (but Desktop works fine)
They will update the list, but not the selection.
Alright, finally resolved this. I turned off the automatic aggregation training. I guess this result is cached. Using the pipeline and re-deploying the report also made the report work (temporarily for a day), but after the refresh, the aggregations resulted in caching, so this was not a long term solution.
The report works as exepcted now. The above is not the solution. The slicer (green box) will update based on the inputs selected.
Anonymous is this a bug? Should slicers be cached? Should there be a feature to supress slicer caching?
That's correct. Numeric parameters or a recipe change will update the selection list (green box). Basically, it's after all the M parameters have been applied, you can further refine the list.
I am debating running a query trace to see what is being sent back to SQL Server.
They will update the list, but not the selection.
Alright, finally resolved this. I turned off the automatic aggregation training. I guess this result is cached. Using the pipeline and re-deploying the report also made the report work (temporarily for a day), but after the refresh, the aggregations resulted in caching, so this was not a long term solution.
The report works as exepcted now. The above is not the solution. The slicer (green box) will update based on the inputs selected.
Anonymous is this a bug? Should slicers be cached? Should there be a feature to supress slicer caching?