Qlik Community

Qlik Sense Enterprise Documents & Videos

Documents & videos about Qlik Sense.

Reload process trigger on external event (e.g. completion of DW load)

New Contributor III

Reload process trigger on external event (e.g. completion of DW load)

The simple attached applications (and sample code) will allow you to setup your Qlik reload processing (in QlikView Server, Publisher or Qlik Sense) to kick off directly on completion of a process on a source system (e.g. an ETL process on a DW).

A simple process.

  1. At the end of the ETL process the source database can be made to write a success value to a specific table in the DB for us to use as an indicator of a successful reload. For example, this might be today's date.
  2. Create a Qlik application (QlikView or Sense) which will be scheduled at the start of the reload process and all other applications will be dependent on this, and any other dependencies they have. This initial application is a simple script that loops until a condition is met by the data being loaded. In this example, when the date loaded from the source DB is equal to today.
  3. This application will be scheduled around the time of the earliest conceived completion of the source DB process or slightly before. This ensures that our reload process is ready and waiting for a completion record, in effect polling the source DB for a completion record.
  4. As this application completes all subsequent reloads will start. This ensures that your reload process kicks off as soon as the source DB has completed processing and never before.

Tip 1 - Add in a pause to the loop so that your application doesn't spam the DB with requests.

A sleep command is added which pauses the reload following an unsuccessful pass. This could be set to every 10 or 60 secs to reduce a constant barrage of requests being sent to the DB. When the condition is met the script will exit the loop before the sleep is activated.

Tip 2 - Multiple triggers to set off different reload streams.

If you have a more complex environment where reload windows are constrained you could setup multiple triggers based on different event outputs from the DW. For example, where the DW completes a sales transactions fact but has many other dependent tables still to process you could have an event written to allow one stream of your reload to commence. The other streams could rely on different event triggers when all table reloads are complete.

Tip 3 - Keep it simple!

I have seen many different ways of setting up processes such as this, most of which IMHO are over-complicating something quite simple. One of the pleasures of working with Qlik products is the relative lack of complexity and the ease of understanding each implementation you come across. This is something we should promote rather than the tendency in IT to introduce/play with another bit of code or tool which makes debugging issues more technical. It also results in hidden steps in the process when someone new is introduced to the implementation, and documentation rarely gets the message across. When I say 'hidden' I would suggest that an initial trigger application in the reload schedule is very clear to someone new to the specific Qlik implementation, actions in source DBs or other programs are not immediately clear and require some digging etc to find and understand.

The example code based on a .txt file in Qlik Sense - change the LIB reference to a defined folder location for QlikView.

LET vDWDate = null();

LET vToday = num(today());

// Start loop script that will continue until condition is met.

Do until vDWDate=vToday


LOAD num(@1) as DWDate

FROM [lib://Trigger/Trigger.txt]

(txt, codepage is 1252, no labels, delimiter is '\t', msq);

LET vDWDate = peek('DWDate');

// where condition is met, exit and complete.

if vDWDate=vToday then

  Exit Do

// where condition is not met, drop that table ready to restart the load process.



// The sleep means that we can control the frequency of calls to the source database (or file).

Sleep 10000;  // 10000 milliseconds = 10 seconds.

end if

// where condition is not met then restart loop.


Try it yourself!

The attached files can be used to test this process.

  1. Download them and have them in the same folder.
  2. Kick off the reload of the QlikView document and watch as it loops through as the condition is not met.
  3. Open the Trigger.txt file and change the date to today's date (format D/M/YYYY unless you change your date settings in the script)
  4. Save the .txt file and watch as the next time the application loops it will complete the reload.
  5. Simple!

Date formats

It is important to match the formats of the dates in both files. Check your global variables in the main tab to understand the settings you are assigning to the vToday variable as this will need to match the data being read from the source to complete the process. The screenshot below shows where to check in Qlik Sense, the same applies in QlikView.


New Contributor III

Hi Anand,

The scheduling is done through the QV server QMC and the process documented here allows a simple approach to check when a DW load has completed rather than assume a time with a set schedule. You still need to schedule this step as the starting point for any reload processing you are doing as a separate QVW or as the first sheet in your script.



New Contributor

Thanks for your response

I want to automate the entire tasks scheduling process. We have autosys agent installed on servers. I am trying to find solution to integrate Autosys and QV. I have gone thru Qlik Community but i don't find any proper document on the same. Can you please share your thoughts on how to integrate QV and Autosys? If any documents  would be really helpful.




Hi Marcus and others,

Qlik Sense doesn't have EDX triggers as such. Sure you can interact with the API, but there isn't a built-in option to trigger tasks on an external event.Regards,


HI Rich,

Thanks for sharing this.

But this will be a problem when multiple triggers are there.

e.g.- In our case. There 30 different clients data will refresh at a different time interval and hence different Database tables are maintained. And we are keeping a single app where all the clients data will be loaded but in a different time interval.

If Client A data is available @11.00 AM the Dashboard will be refreshed at 11.00 AM for client A

If Client B data is available @2.00 AM the Dashboard will be refreshed at 2.00 AM for client B.. and so on.

So there, we are keeping multiple Start Task for each of this client. In such case how can we Trigger the First Task for each client using your methododlogy.


Best Regards



Version history
Revision #:
1 of 1
Last update:
‎2015-09-05 01:28 AM
Updated by: