Hi Pedro,

Thanks for the feedback. We're using TOS Enterprise 5.0.2.

If I create a new Job and drag a table on, it works fine.

If it's an existing Job, I get an "Update Detection" dialog when I edit the Job; but the "Run" Context remains as default even though the contect variables correctly get to the database components.

The solution seems to be to go to the Contexts tab and to re-select the Context Variables. This then adds "Development" and "Test" to the "Run" tab.

I can then delete "Default".


It works; but is time consuming. Is this a bug, the way it is or am I missing something?

Al.

Hi,

I've got two database connections defined (source & target) and I want to update these so that they use context variables.

On the face of this, things seem pretty simple.

In connection one of the dilogues, I can "Export as context". This appreas to associate the Db connection with the newly created Context.

I've configured the Context so that the "Default" is named "Development" and I've added a new "Test".

If I edit an existing Job, I'm given the option to update properties.

This all seems to work fine until I hit the run tab. I can only see a Context of "Default" in the drop-down list rather than "Development" and "Test".

I've managed to get one Job to show "Development" and "Test" by a lot of messing around; but I'm not really sure what the solution was.

Thanks,
Al.