I have a workspace with an FME Workspace Reader where I’m pulling information for ReaderParameters and WriterParameters feature types (don’t need the rest). I’m reading all of the FME workspaces in our FME Flow repository. There is one workspace that returns blank fields for the two ArcGIS Portal Feature Service Readers in the workspace. No other workspaces with ArcGIS Portal Feature Service Readers in them have this issue. I’ve narrowed the problem down to the existence of two User Parameters in the workspace, so I know what the cause is but not why. I can see the feature service info in the FMW file in a text editor so it’s there. In addition, the workspace always reads features from the two services (i.e. - the User Parameters don’t affect the reading of features). Can someone explain why the two User Parameters “block” the feature service info from coming through and how I might fix it? (FME 2023.2.0.0 - Build 23764)
Workspace Reader Feature Reader Parameters Info Is Blank When User Parameters Are Present in FMW
+12- Contributor
Best answer by aaron
I figured it out. Originally, the Default Value for the User Parameter was blank in the drop-down list. After I changed the default to one of the values in the drop-down list, saved and republished the workspace, then the feature service info populated for that workspace in my FME Workspace Reader workspace described above. Must be a bug, in case this obscure issue happens to anyone else using FME 2023.2.0.0.
+20- Enthusiast
I’m not sure if this might be the cause, but check the version of that Feature Reader. I’m on newer version of FME, where we have 2 different version of Feature Reader and they do behave differently.
+12- Contributor
- Best Answer
I figured it out. Originally, the Default Value for the User Parameter was blank in the drop-down list. After I changed the default to one of the values in the drop-down list, saved and republished the workspace, then the feature service info populated for that workspace in my FME Workspace Reader workspace described above. Must be a bug, in case this obscure issue happens to anyone else using FME 2023.2.0.0.