Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content
Announcements
WEBINAR June 25, 2025: Build on Apache Iceberg with Qlik Open Lakehouse - REGISTER TODAY
cancel
Showing results for 
Search instead for 
Did you mean: 
cristinaaguilera
Contributor
Contributor

Caching Issue on Repeated Requests – Help with Advanced Analytics Connection

Hi everyone,

I’m currently working on a dashboard that uses Advanced Analytics integration in Qlik to connect to a server where we compute specific indexes that will be later on be selected by Qlik. Everything is working fine in general, but we’ve encountered an issue and would appreciate some help or suggestions.

I think the problem is that when we perform the same search/query more than once, Qlik sometimes uses cached results instead of sending a fresh request to the server (Do you know if it is the case?). This is causing issues because we need the values to be recalculated each time — they can change even if the inputs don’t.

This is the first time we’re implementing this kind of setup, so we might be missing something in the configuration or best practices.

Attached there is a screenshot of my connection setup for reference.

Is there a way to force Qlik to always perform the request again and not rely on cached results?

Any pointers on how caching works with advanced analytics connections would also be really helpful.

Thanks in advance!

1 Solution

Accepted Solutions
Levi_Turner
Employee
Employee

Try using the key-value pair of ShouldCache and set to False. Example:

endpoints.ScriptEvalStr('{"RequestType":"endpoint", "ShouldCache":"False", "endpoint":{"connectionname":":Get Groups", "parameters": {"request.parameters.filter" :"(subject co \"$(vUserSub)\")"}}}')

View solution in original post

2 Replies
Levi_Turner
Employee
Employee

Try using the key-value pair of ShouldCache and set to False. Example:

endpoints.ScriptEvalStr('{"RequestType":"endpoint", "ShouldCache":"False", "endpoint":{"connectionname":":Get Groups", "parameters": {"request.parameters.filter" :"(subject co \"$(vUserSub)\")"}}}')

cristinaaguilera
Contributor
Contributor
Author

Thanks a lot, @Levi_Turner!
Adding "ShouldCache": "False" to the request did the trick — it's now working exactly as expected. Really appreciate the clear example too, that helped us implement it quickly.