I would like to be able to use the status of an ODX task as a usage condition. For example when my ODX tranfer task completed with errors, I don’t want my MDW transfer job to run. This is my use case but I expect that others might have different use cases for the same feature. Please feel free to share such use cases below.
SUBMITTED
Usage condition based on ODX status
+1+1
+1I think this is similar to what we had in SSIS and SQL Server Agent in the olden days … controls that determine what happens when a task/job succeeds and when a task/job fails. A simple start would be to replicate the OnPrem version’s “Run package” option.
+8I think it would be great to be able to chain packages / jobs together where you have the option to specify a “things went correctly” branch and a “things did not go correctly” branch. Even better would be a visual way to do this as that makes it much easier for a business user to quickly graps what is going on.
The current options for nesting Execution Packages (and using Excluded Steps) vs chaining if things succeed combined with the options Jobs and on-demand ODX Source loads give you makes for a very complex landscape which still has some obvious functionality gaps.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
