For multiple customer scenarios, we needed to fulfil the following requirement:
Setup of recurring batch jobs that are dependent on the output data of each other.
Example:
Batchjob 1 is recurrent and is executed on the 1. of every month.
Batchjob 2 is recurrent and is executed on the 1. of every third month.
Batchjob 3 is recurrent and is executed every on the 1. of every month. Batchjob 3 uses the output data of batch 1 (1st dependency) and the output data of batchjob 2 if the one is relevant for the respective period.
I know it is possible to set this up within one big batchjob, but the limitation is, that all jobs have the same recurrence-schedule.
We used to customize this, by automatically sequencing the generated tasks…
Comments
We are currently building a process that triggers batch jobs in Dynamics to get around this - but its a heavy way to solve this
Category: System administration