Is is possible to a run a report on demand without caching in the browser?

[meddojeddo]

I am running a report on the report server in the browser, and i am running into the issue that when the data is updated, the newly updated data is not immediately visible in the browser because of caching. This can be solved by creating a cache schedule, but is it possible to turn of caching so the data updates when the report is run?

[Anonymous]

Hi @meddojeddo 

Yep, it is possible.

You have to use direct query or live connection.

Direct Query -

Limits your ability to manipulate data in the Desktop (removes the Data section)

Leaves the data in the SQL database

Is "live", no need to schedule a refresh (In the Service)

Check the below video for more details.

[meddojeddo]

@Anonymous I believe this report is using directquery, is there a way I can verify that? I do have the data section though. However I am not on the service, I have uploaded this report to the report server, but I am editing it in Desktop.

[Anonymous]

HI @meddojeddo 

Why not give it a try with a simple table and a slicer. Don't schedule a refresh and on change of the slicer it should get the data from database.

It worked for me although it was bit slow for the turn around time and the volume of data I was using; so, i had to do it through live connection using Python and lambda.

[meddojeddo]

@Anonymous ok so my report is in import mode. However the issue is that when I upload a report in directquery mode to the report server, I get an error saying "Cannot Connect to the Analysis Services server". So I think it needs to be in import mode. Is it not possible to run a report in import mode in the browser without a cache so that the data is up to date?

[DataZoe]

@meddojeddo You can pin the individual visuals to a dashboard (then use that), and then it will keep itself updated as soon as the new data is detected. 

[meddojeddo]

@DataZoe but this is only possible in a workspace and not on the report server, right?

[DataZoe]

@meddojeddo Ohhh, I missed that part of your original question! Yes, that's how it works for a report in a workspace. I am not sure for the report server -- sorry I can't offer anymore help.