Search for all places an attribute is modified or published parameter is used
- kc21
- gdelano
- cshepard
- siennaatsafe
- LizAtSafe
- fmelizard
- david_r
- redgeographics
- geomancer
- danilo_fme
- jdh
- erik_jan
- warrendev
- tcrossman
- vxn43
- carmijo
- davideagle
- fgiron
- lars_de_vries
- geosander
- kennyo
- chriswilson
- jackyd
- milo89
- lambertus
- ciarab
- gbj1717
- revesz
- esko
- radioactivetoy
- tomtoni109
- bigjonas69
- johann
- michaelfitzpatr
- daztreg
- nordpil
- carstenotto
- geolassi
- mikev
- bakkermans
- cwarren
- chickey
- flavien
- zubairsm
- aarongeppert
- mygis
- endest
- ecthelion
- whkarto
- samisnunu
- ekkischeffler
- johnt
- roland.martin
- jneujens
- anari
- rbovard
- tnarladni
- mariofederis
- klingdom
- kweller
- hdlobb
- vijays
- xuhengx
- lpalli
- tomwooldridge
- iangilmour
- willd
- firework_girl
- terrywebber
- geckosolutions
- opowell
- frankers
- kevinwyckoff
- Safer
+51- Safer
- Contributor
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.
+14- Contributor
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.
+16- Safer
+16- Safer
+16- Safer
+16- Safer
+16- Safer
+16- Safer
+16- Safer
+16- Safer
+16- Enthusiast
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.
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.
+16- Enthusiast
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
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.