Skip to main content
Open

When renaming an attribute, have the name-change propagate through the subsequen

Related products:FME Form
  • February 27, 2020
  • 8 replies
  • 36 views
dave_seamless
siennaatsafe
danilo_fme
warrendev
jkr_wrk
+6
  • dave_seamless
    dave_seamless
  • siennaatsafe
    siennaatsafe
  • danilo_fme
    danilo_fme
  • warrendev
    warrendev
  • jkr_wrk
    jkr_wrk
  • dannymeus
    dannymeus
  • alexd
  • karenfirstname
  • mygis
    mygis
  • xabi
    xabi
  • kieran.odonnell
    kieran.odonnell

***Note from Migration:***

Original Title was: When renaming an attribute, have the name-change propagate through the subsequent transformers automatically


Often I find myself in need of renaming an attribute after I've built out complex transformations. If doing so towards the beginning of the workflow, there's the ripple-effect caused by breaking the subsequent transformers containing the renamed attribute, and it can be tedious to make the corrections in the downstream transformers. It would be super useful to have an option for auto-applying the rename downstream from the rename action.

8 replies

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"?


Forum|alt.badge.img+3

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.


  • February 27, 2020

Excellent idea and most helpful.


ebygomm
Influencer
Forum|alt.badge.img+32
  • Influencer
  • February 28, 2020

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 :-)


samisnunu
Contributor
Forum|alt.badge.img+10
  • Contributor
  • March 4, 2020

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.


LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • February 10, 2024
The following idea has been merged into this idea:

All the votes have been transferred into this idea.

LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • September 19, 2024
The following idea has been merged into this idea:

All the votes have been transferred into this idea.

LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • April 2, 2025
The following idea has been merged into this idea:

All the votes have been transferred into this idea.

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings