Skip to main content
Solved

How to use a generic reader with published user parameter for the dataset


buckrogers
Contributor
Forum|alt.badge.img+1

I am creating the desktop version first but it will eventually be published to FME Server so the specific file choice would need to be done using a user parameter.

Ideally, I would like the generic reader to be able to accept any of the following file formats: feature class, shapefile, GeoJSON and CSV.

I have created a published user parameter for File/URL which would allow the user to locate the file they wanted to run through the workbench.

Currently, when I try to add this user parameter in as the Dataset for a generic reader, I get the following error:

Workspace generation failed. Parameter file was C:\\Users\\********\\AppData\\Local\\Temp\\FME_1697209596703_9204.

 

I have also set up a workbench where I tried filtering to feature readers for specific formats e.g. feature class would have it's own Feature Reader where the Format is: Esri Geodatabase(File Geodb) and the Dataset is still my user parameter. However, in this example, it needs to know the name of the feature class(Feature types to read). These feature classes are being created constantly so I don't have those names.

Best answer by nielsgerrits

When using a generic gdb featurereader, it will just read all featureclasses, no need to assign one.

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

7 replies

nielsgerrits
VIP
Forum|alt.badge.img+52
  • VIP
  • Best Answer
  • October 13, 2023

When using a generic gdb featurereader, it will just read all featureclasses, no need to assign one.


buckrogers
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • October 16, 2023

@nielsgerrits​  Thank you for your reply. I have tried setting the Feature Reader format to 'Esri Geodatabase' and the dataset to my published user parameter (which asks user to select a geodatabase) however where I get stuck is the outbound port from the Feature Reader. It requires the fme feature type(feature class name) and without it I have nothing to connect to my next transformer in the workbench. Generic doesn't work.


nielsgerrits
VIP
Forum|alt.badge.img+52
buckrogers wrote:

@nielsgerrits​  Thank you for your reply. I have tried setting the Feature Reader format to 'Esri Geodatabase' and the dataset to my published user parameter (which asks user to select a geodatabase) however where I get stuck is the outbound port from the Feature Reader. It requires the fme feature type(feature class name) and without it I have nothing to connect to my next transformer in the workbench. Generic doesn't work.

I think this is caused by different types of published parameters for different filetypes, Geodatabase being specific different from files or folders. I can't create a workspace with a single published parameter working for all formats.


buckrogers
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • October 17, 2023

I've created a specific published parameter for Geodatabase and another published parameter to filter formats into the right feature reader. The log error is:

ERROR |No FILEGDB dataset name was specified (couldn't find a value for `R_2_DATASET' or `FILEGDB_DATASET')

ERROR |No %0 dataset name was specified (couldn't find a value for `%1')


nielsgerrits
VIP
Forum|alt.badge.img+52
buckrogers wrote:

I've created a specific published parameter for Geodatabase and another published parameter to filter formats into the right feature reader. The log error is:

ERROR |No FILEGDB dataset name was specified (couldn't find a value for `R_2_DATASET' or `FILEGDB_DATASET')

ERROR |No %0 dataset name was specified (couldn't find a value for `%1')

In the workspace you uploaded, the Dataset is empty. You need to set the INPUT_FGDB parameter there.

2023-10-17_14h09_29


buckrogers
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • October 17, 2023

@nielsgerrits​  Right you are! Thank you


nielsgerrits
VIP
Forum|alt.badge.img+52
buckrogers wrote:

@nielsgerrits​  Right you are! Thank you

Cheers :)


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