Thanks, and suspected as much. I guess the question is, has anyone experienced this issue and if so, found a solution? There was clearly something persisting from the previous release. Short of deleting the .share or .meta file, is there a way to selectively eliminate the previous selections? We did try to 'Remove Last Document State' on the AccessPoint, but this did not clear up the issue. We suspect that some object that changed or was deleted in the new version had been previously selected and was skewing the results, but could not be cleared.
Though I have not seen this exact problem described, I read about a problem dealing with cached data. The solution proposed in that case was to restart the QlikView services. Would restarting the QV services following a deployment perhaps correct a condition like this?
Can I delete only the meta file and not shared file. Will this still affect user's shared objects?
I am asking this because I am seeing strange behaviour. The files which are only available for download for authenticated users are not seeing download option. Actually they are not seeing any option. They just see 'Qlikview' written in the place of 'Download' option. I have checked all the task and document properties and the download option is checked with all authenticated users. I am thinking the meta file got corrupted and needs to regenerate.
Thanks in advance,