Skip to main content
Open

Search for all places an attribute is modified or published parameter is used

Related products:FME Form
jnorriskit
danilo_fme
mel
crutledge
nancys
+2
  • jnorriskit
    jnorriskit
  • danilo_fme
    danilo_fme
  • mel
    mel
  • crutledge
    crutledge
  • nancys
    nancys
  • raghavendrans
    raghavendrans
  • mieszkof
    mieszkof

fmelizard
Safer
Across all of workspace, not just current tab. Provide for easy navigation of the reference places. Allows for easy "tracing" of operations affecting an attribute or published parameter.

14 replies

mark2atsafe
Safer
Forum|alt.badge.img+44
  • Safer
  • November 23, 2015
I'm told this is half-complete! Currently works for published parameters, not for attributes. Sorry, not sure if 2016.0 or 2016.1

flavien
Contributor
Forum|alt.badge.img
  • Contributor
  • October 30, 2020

I think a problem with the search is that it returns all AttributeManagers where the attribute appears, even if nothing is done to this attribute. It makes finding what happens to an attribute longer.


whkarto
Contributor
Forum|alt.badge.img+14
  • Contributor
  • May 1, 2023

What happened to this development? It's been quite a while since 2015 and still no such function has been published. Especially in huge workspaces this feature would help so much. I'm so fed up with crawling 20+ AttributeManagers until the one where an attribute has been set can be found.

 

Guys this can't be true by 2023! Please add a "Search declaration" option to the workspace search.


LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • February 8, 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
  • February 8, 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
  • February 8, 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
  • February 8, 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
  • February 8, 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
  • February 8, 2024
The following idea has been merged into this idea:
vijays
All the votes have been transferred into this idea.

LizAtSafe
Safer
Forum|alt.badge.img+15
  • Safer
  • February 8, 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
  • February 8, 2024
The following idea has been merged into this idea:
All the votes have been transferred into this idea.

chriswilson
Supporter
Forum|alt.badge.img+11
  • Supporter
  • January 9, 2025

This could be expanded to include a find and replace for attribute values, e.g. in my case a variation to a URL that is used in multiple locations in the workspace.


david_r
Celebrity
  • January 10, 2025
chriswilson wrote:

This could be expanded to include a find and replace for attribute values, e.g. in my case a variation to a URL that is used in multiple locations in the workspace.

My personal take is to recommend that static information like this should live in a private parameter, so that there’s only one place to modify it.


chriswilson
Supporter
Forum|alt.badge.img+11
  • Supporter
  • January 14, 2025
david_r wrote:
chriswilson wrote:

This could be expanded to include a find and replace for attribute values, e.g. in my case a variation to a URL that is used in multiple locations in the workspace.

My personal take is to recommend that static information like this should live in a private parameter, so that there’s only one place to modify it.

In the case I was thinking of the URL has a dynamic attribute value in the middle so that would need to be nested in the parameter, which it could be.  Sometimes however I think hiding everything in parameters and back-end value configurations etc. isn’t always the way to go, especially when sharing workspaces with less experienced FME professionals for whom it’s sometimes easier to see things laid out in the GUI. 

In my own view having the same text in different parts of the workspace has its place, as does a find and replace, but you do have a point as well.


Reply


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