Replacing QVW for QV Server does not implement changes

[atsushi_saijo]

From time to time, we experience strange issue on QV Server, where developper replaces the QVW file on QlikView Server, however; the users using access point (over Web) do not see the change.

I would rather think it is due to the QlikView Server, loading the QVW on the memory, or possibly http session did not expire, and still accessing to the QVApp, stored on the server side, however; exact mechanism is not known.

Today it occurd again, where developer added additional selection, where it is not implemented on server (however seeing on server locally, it is implemented.)

I often get away this, by logging off, and logging in, and proceed to another tab, and return to the original tab. This somehow shake-up the QlikView, and it is implemented.

I would appreciate any input about what user/server administrators should do.

[Anonymous]

Do you use Publisher and / or Source Control ?

[atsushi_saijo]

Thank you for fast reply.

• On the server, I see only QV Management Console, QV Access Point, and QV server installation.
• Source control is not in place. QVW file is physically replaced.

[#4]

1. How do you have map the server?

2. How developer have define the "Source and QVD"paths

2. Does Qlikview developers have any short of management tools to mange their project and make backups on their projects before they publish to live?

[ashfaq_haseeb · Accepted solution]

Hi,

Make sure allow session recovery is unchecked.

have a look at attached image.

Regards

ASHFAQ

[atsushi_saijo]

• The server is accessed by Remote Desktop, and place it directly on the server. QVW is replaced. As background in this project, we have a developer owing the single business process/reporting, so we do not have source control as single enterprise point. Each developer has own source control (I presume mostly on loading script.)
• Source is defined in the relative path for both row source and QVD. The source folder (where various extraction is stored) is available as a drive. For OLAP purpose, the client prefers making queries on a cloned DB which becomes 1 day old, therefore we have all extractions (which can be jobbed several times per day). OLTP queries are generally prohibited with a few exception.
• For the project management side, yes and all PM group does have various tools. However; I think in general in OLAP project, our delivery due date is shorter than OLTP waterfall development, and design phase is short. Users tend to be more management than operations (i.e. aggragated reports, sales, GL account etc). Data model on the final QVW has been changed often in some cases.
• About backup, currently up to developer (one of them is me). However; I note that in JEE project and when I do development or PM where development takes more time and follows CMMI or particular methodology, the ample tools of source control such as SVN, CVS ... used, but for QlikView where loading script itself can be externalised, and creation of UI is rather short-period, I did not used it. But I am aware that some developer use it, notably Git. I must say source control has itself had some disaster...but maybe this is in the realm of misuse. 😉

[rajeshvaswani77]

On access point make the user to clear last document state, before opening. Hope this helps.

thanks,

Rajesh Vaswani

[#8]

can I know why developer replacing the QVW?

[atsushi_saijo]

Very interesting! I will propagate this to test it. Thank you!

[atsushi_saijo]

Is there any other method than replacing it? (we did replaced at certain window of time). Replacement is in the noon and early evening.