topic Advanced Scheduling with QlikView Publisher in QlikView

Advanced Scheduling with QlikView Publisher

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

Good day,

I have a scheduling request that I don't seen to resolve. I would appreciate any advise in this regard.

Individually I can define these triggers, but I need to manually enable / disable them at the correct intervals, every month. Not good.

I have a request to schedule the loading as follows:

1st Day of the month, load once only at 03:00;

1st Day of the month, reload every hour from 15:00 to 20:00.

Rest of the month, from the 2nd, reload every hour from 03:00 to 20:00.

Thank you very much for your input.

Re: Advanced Scheduling with QlikView Publisher

rubenmarin — Wed, 16 Aug 2017 10:10:02 GMT

Hi John,

One trick -I didn't tried but maybe works- can be setting a document that loads hourly with condition to throw an error outside the desired reload periods. Any non-existant sentence will thrown an error, like "ThrowError"

The main document loads when this document has a successful load.

Or directly set this conditions on the first tab of the document, so it only continues to load on desired time periods.

Another (cleaner, but harder if you don't know it) way can be using EDX:

Using EDX in QlikView 11

Re: Advanced Scheduling with QlikView Publisher

Peter_Cammaert — Thu, 17 Aug 2017 14:02:05 GMT

A variation on Ruben's suggestion (indeed, there is no simple combination of triggers to do this otherwise):

Create a task with an Hourly trigger that runs on every weekday between 3:00 and 20:00
In the load script, check whether the day number is 1.
If it is, check the hour. If we're running between 3:59 and 14:59, let the script fail.
If it's not, proceed as planned and execute the load script.

Best,

Peter

Re: Advanced Scheduling with QlikView Publisher

johngouws — Thu, 17 Aug 2017 22:04:41 GMT

Hello Ruben and Peter.

Thank you very much for the replies.

Peter, I am to set up a test model with this logic and give it a try.

Both answers very correct, but to do this properly, without a work around, one needs to do something via the EDX API.

Thank you.