Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

Not applicable

How AJAX version works? (report version not refreshing for user)

Hello,

I am trying to understand how Qlikview AJAX works... I have published new version of report (changed few columns)

but one of users (opening report in AJAX) is not able to see newly published version - still sees old one without new columns.

How does AJAX really work? does it cache report in browser? If so - how can I be sure that users will always see latest available report? I also spot that AJAX remembers Sheet on which user was before closing report, sometimes even selections made in report.

I tried completely closing browser, reopening it, removing last document state, I am clueless now

Can I force always getting new version of report from server, when using AJAX?

Regards!

Labels (1)
1 Solution

Accepted Solutions
Employee
Employee

Re: How AJAX version works? (report version not refreshing for user)

This could be due to a functionality on the server that allows more than one copy of the document in memory (to allow people to temporarily keep on working although the document is being refreshed).

To force the new document, you can either

  • On the QMC, check "Allow only one copy of document in memory"
  • In the qvw document properties (Server - Refresh mode), set the mode to "Server performs refresh"

HIC

2 Replies
Employee
Employee

Re: How AJAX version works? (report version not refreshing for user)

This could be due to a functionality on the server that allows more than one copy of the document in memory (to allow people to temporarily keep on working although the document is being refreshed).

To force the new document, you can either

  • On the QMC, check "Allow only one copy of document in memory"
  • In the qvw document properties (Server - Refresh mode), set the mode to "Server performs refresh"

HIC

Not applicable

Re: How AJAX version works? (report version not refreshing for user)

Thank you very much for your reply Henric!