Hi @tslack, you might not need to use the GeometryReplacer at all for the city boundary stream. That parameter in the transformer can't accept a featureclass name.
That transformer is typically used to restore geometry previously extracted into an attribute by the GeometryExtractor.
I would use a feature reader to read the city boundary instead. Can you try that route again without using a GeometryReplacer?
Hi @tslack, you might not need to use the GeometryReplacer at all for the city boundary stream. That parameter in the transformer can't accept a featureclass name.
That transformer is typically used to restore geometry previously extracted into an attribute by the GeometryExtractor.
I would use a feature reader to read the city boundary instead. Can you try that route again without using a GeometryReplacer?
@carmijo thanks, i am fairly new to FME and very new to FME server. i guess when using featurereader my question is how to tie that back into the User Parameters. With the GeometeryReplacer for the AOI selection, I am able to specify the geometry source by way of what I named the AOI parameter identifier in the User Parameters 
Right now the input on the app page looks like
Where they have an option to select by AOI or to clip by an existing layer. I've named the parameter identifier in the User Parameters dialog but am uncertain as to how to reference it in the workflow so that when a user selects that option its triggered and when they don't choose it its not triggered.
Thanks again
@carmijo thanks, i am fairly new to FME and very new to FME server. i guess when using featurereader my question is how to tie that back into the User Parameters. With the GeometeryReplacer for the AOI selection, I am able to specify the geometry source by way of what I named the AOI parameter identifier in the User Parameters Right now the input on the app page looks like
Where they have an option to select by AOI or to clip by an existing layer. I've named the parameter identifier in the User Parameters dialog but am uncertain as to how to reference it in the workflow so that when a user selects that option its triggered and when they don't choose it its not triggered.
Thanks again
my first thought was a testfilter but i didn't have a much luck. i guess in my head the testfilter needs some way of looking to see if the user parameters value for LAYERCLIP (what i called the parameter id) = 'City Boundary' but I cant quite find a format that works for that.
EDIT: You put me on the right track confirming I had to use featurereader.
I managed to get this working by using parameterfetcher and passing that into an attribute and using a testfilter on that. Thanks!
@carmijo thanks, i am fairly new to FME and very new to FME server. i guess when using featurereader my question is how to tie that back into the User Parameters. With the GeometeryReplacer for the AOI selection, I am able to specify the geometry source by way of what I named the AOI parameter identifier in the User Parameters Right now the input on the app page looks like
Where they have an option to select by AOI or to clip by an existing layer. I've named the parameter identifier in the User Parameters dialog but am uncertain as to how to reference it in the workflow so that when a user selects that option its triggered and when they don't choose it its not triggered.
Thanks again
You could set it up like this where the featurereader feature types to read are taken from the user input of the 'clip_layer' paremeter. If a user draws a polygon to clip by, it will be used. If a user selects a layer to clip by, it will be used instead. In this example, the user would need to put something in one of the two parameter or nothing will happen.
---
If i've provided something helpful, please upvote the comment. If i've provided a solution, please mark it as 'Best Answer'. This marks the post as answered and helps the community find the solution. If I didn't provide a solution, please let me know if I can help further. Thanks! 🙂
@carmijo thanks, i am fairly new to FME and very new to FME server. i guess when using featurereader my question is how to tie that back into the User Parameters. With the GeometeryReplacer for the AOI selection, I am able to specify the geometry source by way of what I named the AOI parameter identifier in the User Parameters Right now the input on the app page looks like
Where they have an option to select by AOI or to clip by an existing layer. I've named the parameter identifier in the User Parameters dialog but am uncertain as to how to reference it in the workflow so that when a user selects that option its triggered and when they don't choose it its not triggered.
Thanks again
Thanks for the response. I'll try this out and see if its any faster. I managed to come up with this that seems to work so far
my thought was I could add a second geometryreplacer, set the encoding to OGC well known text and the source as $(LAYERCLIP) by when I run it and select the City Boundary to clip but FME gives me the error INVALID_PARAMETER_GEOMETRY_SOURCE. Is it because FME doesn't know what GISOWNER.city_boundary is? Its a layer in our enterprise SDE. I tried adding in a featurereader to read the layer before it goes to the replacer and had no luck.