topic Re: QlikView Reload Issues in QlikView

QlikView Reload Issues

pandiarajan — Mon, 26 Jan 2026 18:19:17 GMT

Dear All,

We are getting one weird issue in one of our QlikView Dashboard. We are getting a different value in Qlikview Dashboard between running QMC and through Manual Reload or windows task scheduler. We are reloading the same application through windows task scheduler for Export Excel. Even though we have removed the section access and reload but still we are getting different value

Re: QlikView Reload Issues

pradosh_thakur — Tue, 12 Feb 2019 04:50:57 GMT

1: Can you copy paste the code in a new qvw ans see what results you are getting

2: Do you have binary load ?

3: Do you have a .prj folder ?

Re: QlikView Reload Issues

pandiarajan — Tue, 12 Feb 2019 05:05:10 GMT

Thank You For Quick Response Pradosh

1) Can you copy paste the code in a new qvw ans see what results you are getting - Yes I have done still i am getting Same Wrong Value

2: Do you have binary load ? - Yes

3: Do you have a .prj folder ? - No

Re: QlikView Reload Issues

marksouzacosta — Tue, 12 Feb 2019 05:22:33 GMT

Will be nice to see the app. Can you share it with us?

Re: QlikView Reload Issues

pradosh_thakur — Tue, 12 Feb 2019 05:28:52 GMT

A couple more things
1: Is your data updated in both qmc/server folders and your local one. If the qvds are not uodated the data may be different
2: Does your binary load file has section access

You can post the app if this checks doesn't help you so Mark can have a look. I don't have the license so hopefully he can help you solve this.

Thanks
Pradosh

Re: QlikView Reload Issues

Bill_Britt — Tue, 12 Feb 2019 13:27:17 GMT

Hi,

When you are doing the reloads, are you using the same login account? Is there Section Access applied to the document?

Bill

Re: QlikView Reload Issues

Brett_Bleess — Thu, 28 Feb 2019 21:20:20 GMT

What I would do in this case is be sure you are running the Script/Document logging and compare the lines fetched on each pull in the app from the two different runs to figure out which table is missing record(s), as once you know that, then should be easier to try to explain what may be happening at that point. Hopefully this makes some sense.

To Bill's point, I would probably run with Section Access commented out to take that out of the equation for the moment and be sure the data pulls tie out that way, and if they do, then uncomment Section Access again and recheck things in the logs that way...

Regards,
Brett