Would be great if within TX (or via external script) you could trigger Data Source transfer tasks as an initial Step within an Execution Package (or batch), so that once the transfer of new data is complete, the execution package runs the next dependant step? This way, if the transfer task from the data source to the DL takes longer (more data than expected) then the execution package won't run until it completes. There seems to be no method currently to trigger a transfer load within the execution packages - and therefore no way to make the two different scheduling tools (it's really that) align with each other intelligently.
Solved
Trigger Data Source transfer tasks from Execution Packages
Best answer by Trine Stuhr
Hi Jon,
Thank you for your suggestion (and our apologies for a bit of a late answer). In the newest version of TimeXtender (release last week), you can trigger data source transfers as the initial step before an execution package - we call this new feature ODX On-demand. Please check out the latest release notes in here: TimeXtender 6143.1 | Community and this KB article for further explanation and guidance on how to use this feature: Scheduling Executions using Jobs | Community (timextender.com)
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.