Preserve Index of Inactive Tasks
When you mark a task as inactive in your ETL, it becomes impossible to add another rule later on and have the index of the new rule be greater than the index of the inactive task. I believe what is happening is that when you drag and drop rules around to affect the order, ADMM is always putting inactive tasks at the end of the ETL. This can have really disastrous consequences if you have a task that is inactive temporarily - i.e. for debugging purposes, load cycle purposes, remediation purposes, etc. If you have a task inactive just temporarily and try to change the order of the existing index or add new ones, they will go to the bottom and now your ETL order is destroyed. I would love for ADMM to preserve your index order regardless of active/inactive - the order is super critical to the overall execution and the system should not be changing this automatically.
Log in to comment and vote
Comments1
JasenSlate
Dec 2, 2025
To add to this - the Active/Inactive status should not be a factor in the re-numbering of the ETL index.
If you temporarily deactivate a task and adjust the order of another rule in the sequence - the Index re-numbering process is called and the relation that the deactivated rule had in the over-all order is lost.
The deactivated value keeps the old index value that it had, and an active rule may be given the same Index number - which makes the transformation sequence look disorganized/messy.
If you have many fields in your target mapped as rules - the ETL tasks and views get created for them. You might be able to update many of the fields off of a single update, which leaves you with unnecessary ETL steps that can’t be deleted so you have to mark them as disabled.
The only Option for these is to keep them disabled in Index zero so they don’t get mixed in with the legitimate update rules.
It is incredibly frustrating.