Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
When reloading a document is it okay for users to be using the document? What sort of issues will this cause for the reload or user experience?
Nick
From the help
On this tab define certain aspects of the document's behavior when run on a QlikView Server.
Refresh Mode when Document is Updated on Server
This setting defines how an updated document on the QlikView Server will be handled.
Client initiates refresh. If old data not kept in server or client too old, session will be disconnected. | Choose this option if the server should never initiate a refresh of data in the client automatically. When a new version of the document becomes available on the server, the client will be offered to refresh according to the preferences set under Client Refresh Initiation Mode below. If this is not possible, either because the client is too old (pre version 😎 or if the server is set with Allow only one copy of document in memory enabled in the QlikView Server control panel, the session will simply be terminated. |
Client initiates refresh. If old data not kept in server or client too old, refresh will be performed automatically | Choose this option if it is preferred to let the client initiate a refresh of data in the client when possible but will allow server to initiate a refresh automatically if necessary. When a new version of the document becomes available on the server, the client will be offered to refresh according to the preferences set under Client Refresh Initiation Mode below. If this is not possible, either because the client is too old (pre version 😎 or if the server is set with Allow only one copy of document in memory enabled in the QlikView Server control panel, the refresh will be performed automatically by the server. |
Server performs refresh automatically, without client action | This is the option to choose if you prefer to always let the server initiate a refresh of data in the client automatically. When a new version of the document becomes available on the server, the data in the client will be refreshed. |
Client Refresh Initiation Mode
This setting defines how the client should be notified of the availability of new data on the server and initiate a refresh. This setting is only valid when client initiated refresh has been selected in Refresh Mode when Document is Updated on Server (see above).
Indicate with toolbar button | The availability of new data is indicated by the Refresh button in the toolbar turning green and being enabled (and the corresponding File menu command being enabled). The refresh is performed at a time of the user's choice by clicking on the toolbar button or by means of the File menu Refresh command. |
Prompt with dialog | In addition to the Refresh button in the toolbar turning green, the availability of new data will be indicated by a prompt dialog. In the dialog the user may choose between immediate refresh or wait, in which case the refresh can be performed at any later time of the user's choice by clicking on the toolbar button or by means of the File menu Refresh command. |
Just do it but tell the user it is happening | The refresh will be initiated as soon as the server indicates that new data is available. A dialog will be shown to indicate that the refresh is taking place. |
Just do it | The refresh will be initiated as soon as the server indicates that new data is available. No dialog will be shown to indicate that the refresh is taking place. The user will experience a document "freeze" lasting from fractions of a second up to minutes depending on server settings and size of document. |
QlikView 11.20 SR12
You can reload without problems.
It depends on the setting you have in your QVW what your users will experience. In some settings the data will just be refreshed, in others they will get a message about it. There are a few options.
I am not doing the development of the documents. Can you direct me to a document that lists these options so I can speak to the developer?
To state few best practice:
1.Do not directly work by opening the document from the server because it consumes lot of memory. Instead copy to you local environment and work on the same.
2.Do not open the document or folder when the reload is happening.
3.while reloading the users can access the document from Access point without any issues, but once the reload is complete the document might get refresh so that the user will get the updated data. etc
In your local QlikView client go to "Settings" -> "Document Properties" and open the "Server" tab. The two dropdown boxes at the top give you all settings related to how the document behaves after a reload.
From the help
On this tab define certain aspects of the document's behavior when run on a QlikView Server.
Refresh Mode when Document is Updated on Server
This setting defines how an updated document on the QlikView Server will be handled.
Client initiates refresh. If old data not kept in server or client too old, session will be disconnected. | Choose this option if the server should never initiate a refresh of data in the client automatically. When a new version of the document becomes available on the server, the client will be offered to refresh according to the preferences set under Client Refresh Initiation Mode below. If this is not possible, either because the client is too old (pre version 😎 or if the server is set with Allow only one copy of document in memory enabled in the QlikView Server control panel, the session will simply be terminated. |
Client initiates refresh. If old data not kept in server or client too old, refresh will be performed automatically | Choose this option if it is preferred to let the client initiate a refresh of data in the client when possible but will allow server to initiate a refresh automatically if necessary. When a new version of the document becomes available on the server, the client will be offered to refresh according to the preferences set under Client Refresh Initiation Mode below. If this is not possible, either because the client is too old (pre version 😎 or if the server is set with Allow only one copy of document in memory enabled in the QlikView Server control panel, the refresh will be performed automatically by the server. |
Server performs refresh automatically, without client action | This is the option to choose if you prefer to always let the server initiate a refresh of data in the client automatically. When a new version of the document becomes available on the server, the data in the client will be refreshed. |
Client Refresh Initiation Mode
This setting defines how the client should be notified of the availability of new data on the server and initiate a refresh. This setting is only valid when client initiated refresh has been selected in Refresh Mode when Document is Updated on Server (see above).
Indicate with toolbar button | The availability of new data is indicated by the Refresh button in the toolbar turning green and being enabled (and the corresponding File menu command being enabled). The refresh is performed at a time of the user's choice by clicking on the toolbar button or by means of the File menu Refresh command. |
Prompt with dialog | In addition to the Refresh button in the toolbar turning green, the availability of new data will be indicated by a prompt dialog. In the dialog the user may choose between immediate refresh or wait, in which case the refresh can be performed at any later time of the user's choice by clicking on the toolbar button or by means of the File menu Refresh command. |
Just do it but tell the user it is happening | The refresh will be initiated as soon as the server indicates that new data is available. A dialog will be shown to indicate that the refresh is taking place. |
Just do it | The refresh will be initiated as soon as the server indicates that new data is available. No dialog will be shown to indicate that the refresh is taking place. The user will experience a document "freeze" lasting from fractions of a second up to minutes depending on server settings and size of document. |
QlikView 11.20 SR12