Keep job details when switching connections

[bwmodular]

Hi, an enhancement request for this already awesome tool.

If you change connections when using BDU, it would be great if you were immediately able to re-run the same job in the new environment. Instead, it resets the fetchXml to an empty query or sometimes populates the fetchXml with a query that was run in some other session a while ago it also sometimes populates the selected attribute to update to be one from a previous job, or sometimes clears the selected attribute and kind of locks the 'Select Attribute to Update' section so you have to reset the attributes to get it working again.

Ideally, if I run a job in environment A and then switch to environment B, I'd like to be able to just carry out the same job in Environment B without having to make any other changes.

I'm sure it's realy hard to handle this switch in connections so just thought I'd raise it in case it's something you'd think about looking at.

Thanks!

[rappen]

Great idea!

How about this? Show when connected to another connection.