Anyone have easy instructions for Triggering an application to auto reload data from an OLEDB connection? Either when the app is opened or when source data is updated.

[leale1997]

I am new to qlik and need to set an application already deployed to a server to auto reload data when the application is opened.  The application is loading data via an OLEDB connection.

[jonasheisterkam]

You can take a look at direct discovery.

You can Setup the Server to the following option

Allow Only One Copy of Document in Memory

If there are changes to a document, for example, a reload or a layout change, the QVS can be configured to do either of the following options.

• Force an immediate update of the document for the user during the session, that is, allowing only one version of a document. This will conserve memory resources on the QVS.
• Await a new session, then update the document for the user. This may cause several copies of different versions of the document, residing in memory at the same time.

To allow only one version of the document in memory, tick this check box. To allow several versions of the document in memory, untick this check box.

You can reload permanently, but a check on the start of the skript would be a good to compare if you need to load the data.

[leale1997]

Hi!  Thanks so much for the assist

Apologies, again, new to qlikview.  It sounds like you are describing a server setting and not a setting within the application? 

I am with a large company and don't think they would adjust server settings for just my application.  Is there a way to add an "update on Open" command to the script for just my application?

[jduenyas]

You can set up the document in Settings>Document>Triggers>OnOpen and add a Macro that will run a command such as :

ActiveDocument.Reload

ActiveDocuemnt.Save

But why would you like to do that if there many people using the document which will trigger many reloads (time consuming and confusing to users)?

Better set the Document to reload on set time-intervals such as every 15 or 30 minutes.

[Anonymous]

...or maybe even "continuous" reload...

[Anonymous]

Well, it is a reload task for application and it is to be configured on QV server.

[jonasheisterkam]

If you want to use it on the QV-Server you need to do it on the serverside.

You can enable external Trigger to reload the document but this option would be a bigger impact and you need a webservice which would call from the document. If you control the datasource you can look if you can trigger external program on database change, the external program is then the external trigger in qv-server.

If direct discovery is enabled on the server it is the way to get near as possible to the livedata without extension.

If youre etl process is simple you can take also a look to patial reload.

[leale1997]

It sounds like this is a setting that should be controlled by the server administrator.

I have sent a note to my QVS administrator and asked him for better guidance.

Thanks for all of the feedback!!