You are not logged in.
You will see this windows(the following image) after you finish "Export as Context".
One time you can choose only one context group for this metadata->DB Connection.
I don't think it's a bug.
You have to drag and drop the context manually. ..
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?
Welcome to Talend Community!
Which version do you use? If you are using TOS 5.1.1, it allows you drag and drop this context group with both Dev and Test into a job correctly.
However, for the previous version like TOS 4, it may lose Test context group. It was a bug.
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.