Trigger Data Source transfer tasks from Execution Packages

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.

Page 1 / 1

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)

Hi Jon,

Hi Trine - that’s great, and thank you for responding.
So, how/when can I upgrade from 20.10.26.64 - if I need to upgrade from 20.10 to v21(6117) first then can you point me to documented instructions on how to perform that upgrade - my searches are coming up empty - trust you can help.

Jon.

Hi Jon,

We are currently working on a migration tool, that will allow you to upgrade from 20.10 to the latest version (currently 6143.1). We will release documented instructions when the migration tool is available.

Hi Christian,

Do you happen to have a timeline for the release of this migration tool?

Hi Daniel,

We do not currently have a timeline for the release of the migration tool.

Reply

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded