Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.Join Us
When Removing Last Document State on a document from AccessPoint, the expectation is any selections made before should be removed when accessing the document again.
When Removing Last Document State on a document from AccessPoint, the selections made before that removal remain when accessing the document next time.
When going from the document to the AccessPoint, without closing the session, no session recovery information is saved until the web server lets the QlikView server know the session has ended which is dependent upon the Inactive Session Timeout in the QlikView Server settings.
If the session has not actually ended, there is no document state to remove from the shared file when "Remove last document state" is pushed. What occurred in 11.20 SR13, was that the old session was closed (without saving the state) and therefore a new one was started when going back to the document.
In later versions, the open session is re-used when going into the document again if the session has not timed out. The change is an intentional consequence of a bug fix. Prior to that fix, the webserver always started a new session and did not correctly detect that the user already had an ongoing session on that document. Using the back arrow does not close the session.
To get the expected behavior, it is necessary to click the 'Close' link in the upper right corner of the app before using the back arrow. So when using the back arrow, there is no "Last document state". Thus, pushing the button does not do anything.
Attempting to click the 'Close' link before the back arrow, will result in the expected behavior by removing the "Last document state".
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.