Skip to main content
Solved

Generic source file name confusion? Or bad workflow?


cs_vt_psd
Participant
Forum|alt.badge.img+1

I’m working through a data cleaning process in a workspace. I have multiple files that are different from each other in schema and attributes, but are essentially all saying similar things. Hence the cleaning.

 

I’m working in one workspace to make re-use of transformers a little easier, but when I’m using the FirenameParkExtractor transformer I need to identify a user parameter source for it to gather up a name to chop up. This is what that dropdown looks like:

 

The names here do not align with how I’ve named the readers and associated files so I’m a little confused about how to make this situation easier to work with. I’d like to be able to rename the source datasets, but I’m not sure where I’d do that. Can you tell me?

 

As an aside, is it a bad idea to process many things in one workspace? Should each file get it’s own? Is there some helpful documentation out there about designing workflows? (I’ll be searching on that just now, but I thought of the question as I was writing the post!) Happy to field tips from more experienced FME handlers.

 

Thanks!

Best answer by hkingsbury

Those parameter IDs are the defaults when a reader is added. You can change those by opening the Manage User Parameters window from the navigator and changing the Parameter ID to something clearer

 

 

View original
Did this help you find an answer to your question?

2 replies

hkingsbury
Celebrity
Forum|alt.badge.img+55
  • Celebrity
  • Best Answer
  • July 16, 2025

Those parameter IDs are the defaults when a reader is added. You can change those by opening the Manage User Parameters window from the navigator and changing the Parameter ID to something clearer

 

 


cs_vt_psd
Participant
Forum|alt.badge.img+1
  • Author
  • Participant
  • July 17, 2025

@hkingsbury that worked! Thanks for your guidance here.


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