Robust or Sticky Transformation Mode?

Hellos,

I have a transformation I have spent days making & it's working fine , now I am required to add two more fields from the input , to the output , when I add the fields back , all the mapped transformation are moved down (with the new index number?)

if my blabbering are not making sense , please see LOOM VIDEO

Please see before & after attachment.  

Suggestions
1. Lock Mode which doesn't move the existing transformation ?
2. Ability to sort the columns so added columns can be at the bottom 

 

The mapping is position based so if you insert new field in the middle your mapping would be shifted down.

Right now the only way to deal with this, is to stick another transformation after fields selector and use auto map.

Another option Is to extend Fields Selector functionality by adding ability to sort fields (that should not take long).     

Another option Is to extend Fields Selector functionality by adding ability to sort fields (that should not take long).     

Re-Ordering Columns can be very helpful. Will become my default after every reader to fool proof for future

Specially in testing phase , when input file can bring new fields !!

Another suggestion will be usage of 'decoy label' (Blank inputs), since inspite of re-ordering the column , the transformation downstream will still be affected. 

Since my item is input is sql query , I can get around currently by introducing two empty columns, but above feature can be useful if the upstream there is another transformation. 

Any thoughts on this ? 

Sorry we have not had a chance to have a look at it yet but we will.

It is included into the development plan.