Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Save $650 on Qlik Connect, Dec 1 - 7, our lowest price of the year. Register with code CYBERWEEK: Register
cancel
Showing results for 
Search instead for 
Did you mean: 
Steve_P
Contributor
Contributor

Qlikview showing old objects for a user

Hi,

We are using Qlikview served to the user from the QV server to Edge or Chrome e.g. http://qlikview1/QvAJAXZfc/opendoc.htm and occasionally for a user, they receive old objects on their report and some objects appear incorrectly i.e. listboxes which no longer appear in the QVW and haven't for sometime, a year or more. It only affects a single user. Copying the file to a new name and the user requesting that in the browser fixes the problem i.e. the old object don't appear.

I have deleted the .QVW.Shared file from the file system. The user has tried different browsers. One guess is that there is an object on the QV server, but I don't see one to clear. 

This has previously been resolved by adding a listbox or other UI element to the QVW and saving, but on this occasion, nothing seem to work. 

Does anyone know why this happens and how to resolve?

Thanks,

Steve

 

Labels (2)
1 Solution

Accepted Solutions
Steve_P
Contributor
Contributor
Author

Thanks very much for the info, it allowed me to rule out some things. It turned out to be something a bit more simple - there was an old sheet in the QVW that was a copy of the main sheet and the user had managed to navigate to that, despite there being no clickable buttons to it (perhaps there is a keyboard combination in the browser that allowed it). Anyway, I'll delete the old sheet that caused these problems.

Thanks for replying.

View solution in original post

2 Replies
marcus_sommer

Removing the shared-file (after a BACKUP) is a good way to eliminate strange issues within the access point. Using different browsers is also helpful but to be sure to exclude them as cause you should also delete the browser cache. A further possibility is the feature of session recovery which could be reset by clicking the small green link "show details" within the access point below the application and there "remove last document state".

Beside this such things could happens by the use of section access and/or any user-related condition within the sheets/objects - whereby if this didn't happens anymore by a copy the application it shouldn't be the cause in this case.

Steve_P
Contributor
Contributor
Author

Thanks very much for the info, it allowed me to rule out some things. It turned out to be something a bit more simple - there was an old sheet in the QVW that was a copy of the main sheet and the user had managed to navigate to that, despite there being no clickable buttons to it (perhaps there is a keyboard combination in the browser that allowed it). Anyway, I'll delete the old sheet that caused these problems.

Thanks for replying.