Variable Mapping in Data Integration Studio Keeps Changing

[Yiping]

Hi Everyone,

I just started using Data Integration Studio, and I've learned to use the variable mapping tool in Extract transformation to remove the variables that I don't need. However, I noticed that the mapping would change every time I made a change in the later part of the job process. This caused me troubles because I have to go through all the transformations to do the mapping again. Is there a way to lock the mapping so it won't change once it's configured?

Does anyone have a solution to this? Or is there a better way to select the variables in Data Integration Studio?

Please refer to the attached screenshots for more details.

The screenshot below shows the configured variable mapping:

The screenshot below shows the mapping returned to the what it was before the configuration when I did some change in other transformation. 

Any advise would be appreciated. Thank you very much! 

[Patrick · Accepted solution]

What I normally do is to deactivate below two setting after the initial configuration of a transformation.

These two settings are useful to speed up the initial setup but can "involuntarily" change your mapping as an effect of changes to the source or target table metadata structure.

You can also decide to turn the settings off by default under Tools/Options

[Yiping]

Hi Patrick,

Thank you so much for your reply! Yes, it works!

Thank you!

Yiping

[ErikLund_Jensen]

Hi @Patrick 

Turning the settings off by default doesn't seen to work. I have tried in many DI Studio versions over 12 years (present version is p.t. 4.903), and disabling automap and autopropagate in tools -> options never had any effect on new transformations, no matter if the job is new or old. The same goes for auto join conditions, which I prefer disabled too.

We use a workaround with a weekly batch job that turns the setting off on all transformations, but the auto settings still causes many unwanted columns all over our warehouse, so it would be better to have them disabled from the beginning and do all mappings manually. 

Have you ever seen it working in person, and if yes, do you have any ideas to help us to get it working? Any ideas would be highly appreciated

Erik

[Patrick]

Hi @ErikLund_Jensen 

Should have thought a bit more when proposing the options setting. No, it hasn't worked for me either and it just became over the years a work practice for me to turn it off for every single transformation. I can't remember though that "unticking" doesn't stick once set.

I've just tested with DIS4.904 and the behaviour hasn't changed. 

I assume that the option is on job level and though gets overwritten by transformation level - without a way to change the default on transformation level.