Skip to main content
Question

Feature Writer does not Uses OutPut File geodatabase name from the User parameter on FME Flow.It works fine on FME Form


fme_can_do_it
Enthusiast
Forum|alt.badge.img+11

Parameter2featureWriter1FeatureWriter2After processing the data, I am using the Feature Writer to write the output into a file geodatabase. I have configured the Feature Writer to use the User Parameter name as the output geodatabase, which means that the database name should change every time I input a new name in the User Parameter field. Although I am getting the desired output file geodatabase every time I run the workspace in the FME Form, the same workspace does not change the output geodatabase name when I run it on the FME Flow. Using Version 2022.2.2 for FME Flow and Form. I would greatly appreciate any help to fix this problem.

2 replies

redgeographics
Celebrity
Forum|alt.badge.img+50

In order to help you it would be good if you could share some screenshots of how you've set up that parameter. I think it would also be good to know which service the workspace runs under (Data Download or Job Submitter).

 

Can you create an attribute, fill it with that parameter value and then add a Logger so you can inspect it in the FME Flow logfile?


fme_can_do_it
Enthusiast
Forum|alt.badge.img+11
  • Author
  • Enthusiast
  • January 11, 2024
redgeographics wrote:

In order to help you it would be good if you could share some screenshots of how you've set up that parameter. I think it would also be good to know which service the workspace runs under (Data Download or Job Submitter).

 

Can you create an attribute, fill it with that parameter value and then add a Logger so you can inspect it in the FME Flow logfile?

@Hans van der Maarel​ I have just added screenshots of the feature writer properties to the message thread. The workspace runs under Data Download service on FME Flow.


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