Discussion Board for collaboration related to QlikView App Development.
Do any of you have this problem?
Lately (QlikView V.12) rejects all changes to my dashboard, both in the visuals as in the load script. It occurs right after a save, or even just before saving!
Very frustrating, as you lose all work you have done in the last few hours!
It doesn't happen very often, just now and then, but I get tired pressing Ctrl+S 300 times per hour....
It happens both locally and while working with QlikView on RDS (from home).
Solved! Go to Solution.
Hi Marcus, I agree. A collegue had the very same problem more than a year ago (I had a hard time believing him..), and this was far before any major update.
I'll let it rest for now. Everyone a warm thank you for your suggestions.
I would check the timestamp of the files within the explorer after saving them and before closing QlikView - and then closing QlikView and checking again. It should give a clear hint if QlikView is the cause - I rather doubt it. After bigger work I would also copy one as a backup. Further helpful might be to enable the creation of copies within the user-settings in tab saving.
If QlikView is not the cause I would suspect problems with your storage, user profile or any security tool.
I rather like your suggestion to create copies through user settings. Although: This morning QV reverted to an older situation WITHOUT saving or (re)loading, so I still suspect the cause to be QV...
I just saw a short blink on the screen and I got the old situation back (from an hour before).
If the file was really saved I don't see much possibilities how Qlik could revert to an older version - from a Qlik point of the view there is just one. If this really happens I would assume the cause rather by a security tool or any service (indexing, windows shadow copies and similar) which might block the current version and providing an older one. Therefore my suggestion with checking the timestamps.
Beside this which filesystem is used - AFAIK only windows is supported and no NAS.
Recently I saw a message about an incompatibility from Sophos and the last Windows updates ... Maybe google could deliver more details to it whereby I think other causes would be more likely.