Saved QVW files that do not save....

[Anonymous]

I thought that would get your attention.

Quite often I am called on to make minor changes to our reports.  You know how it is, the end user wants that pivot table but split by patient not month.

So, I open the report up, make the change, save it close it.

Go through the web portal to check how it looks and the change is not there.   Make the change again (quicker this time because I'm a quick study!) save it again.  back to the web portal and bingo, my change is now there.

I've been working with Qlikview for 3 years now and nothing substantial has changed with our server, the location of our files on the server or much else for that matter.  Yet, every now and then, when you least expect it.  The changes you save.... do not save.

I would think that access rights would present themself in a denial message upon trying to save.  but this never happens.  my file saves quickly and without complaint.

I have a theory and it involves a piece of information I haven't shared with you yet.

Some of our more popular reports are set to server reload every 15 minutes.  This is to pick up new users that might be added to the Section Access list.  Its a bit cludgy but at least this way, when a new user is added we can tell them they will have access in 15 minutes.

I wonder if Qlikview server sometimes overwrites my new change with what it pulled into memory just prior to me opening the file?  It seems possible to me that if the timing is right, it could open the file for reload, I also open the file, I make my change then save and close, QV completes reload of its version and saves/closes.  the last copy saved overwrites the other one.  this could happen.

has anyone had this happen to them?  if so, what are your thoughts?  and if I'm right, what should I do?  suspend the reload while I work on the file?

thanks,

John.

[advait_thakur]

Hello John,

Sounds strange, I never face such thing.

Do you mean that your app is saved always second time and then the change appears on web.

Are you sure that you refresh frequency interval always's happens followed by your change.

I believe there must be some other activities going on server same time.

How often this happens? Always/ sometimes/ rarely?

Yes,so believe your theory.

I was wondering so just made a thought.

Thanks,

Advait

[rwunderlich · Accepted solution]

Hi John,

If you are not using Publisher than your explanation is quite plausible and I have had it happen to me. You can cover yourself by checking that any reload has completed before you save the file.

-Rob

[Anonymous]

I bet the explanation is correct.  Seen this, also in the environment where reload is running often.

Yes, a reliable way to deal with it is to disable reload before saving the new version.

Regards,

Michael