When renaming an attribute, propagate name change to downstream/subsequent transformers

Great idea , I would add to this request the Option to have it rename throughout the workspace... maybe a pop conformation "Rename yes / no box"?

As Chris Taylor noted below, an option to make the rename be 'global' would be useful. Perhaps give the user an option in a pop confirmation to have it be a 'global' , or a 'downstream from here' rename.

Excellent idea and most helpful.

I'm sure I'm not the only one who has kept a typo in an attribute name and then renamed at the end rather than unpick changing it throughout a workspace :-)

Oh yes please, we need this!

That makes sense and reduces the maintenance time of a workspace and increases productivity.

I guess this idea is already implemented to published parameters, but not feature types attributes inside transformer.

For me I would say that when saving a change in FME whatever code gets run to identify transformers pointing to broken or missing references should do some magic to try to identify whats changed. Perhaps you can right click on a transformer and select “update references”. Similar to updating transformers. You could select multiple at once or maybe there is a way to do all transformers at once.

In this case scenario 3 for me I would assume it would break/prevent any downstream changes because the transformers would still be valid. A feature like this might actually prevent such bad behaviour :-D.

Definitely trust will be an issue. But my god do I want something like this. 

 

+1 - possibly with the option to allow this to happen e.g. ‘Rename Downstream’ vs the regular ‘Rename’.