Skip to main content
  • EN

On FME Flow we added a Network Based Resource. In FME Flow, I can see that the system path of this Network Based Resource is characterized with a parameter, e.g. '$(My_Network_Based_Resource)'.

 

I had some trouble on using that parameter in a workspace with FME Form Workbench. FME Form is not aware that this parameter exists, and upon using it in e.g. a path reader.

Is there any way that you can expose additional FME Flow parameters to FME Form Workbench?

 

As a workaround I was able to use a ParameterFetcher, and then feeding in the attribute value of the Network Based Resource into the FeatureReader, but that seems not ideal. Also, the ParameterFetcher does show a Red Cogwheel, because it is not aware of the parameter.

 

Another alternative is probably to create an additional 'FileURL' type of parameter, and set the (default) value for that parameter to '$(My_Network_Based_Resource)'. However, also here it seems that you are then forced to make the FileURL parameter optional, as otherwise you will not be allowed to enter the unknown parameter for its value.

 

Lastly I found it possible to edit the *.fmw file in NotePad++ to edit the path in the FeatureReader to the parameter '$(My_Network_Based_Resource)'. But editing workspaces in NotePad++ is not really the recommended way I would say...

 

So long story short, I'm mainly wondering what the intended design is to use the (system path) parameters of an FME Flow Network Based Resource in FME Form Workbench.

 

See below workbench for an illustration;

imageN.b. When I dealt with this problem, it seemed that a 'Generic Path FeatureReader' would provide an error in case it was configured with the unknown FME Flow parameter '$(My_Network_Based_Resource)' (i.e. that using a ParameterFetcher was the only option), but in the current setup with a regular Path FeatureReader it does seem to work.

 

Hi @thijsknapen​,

 

I like the idea of being able to directly import the list of Resource parameters directly from FME Flow into FME Form. That's worth posting as an idea.

 

What I usually do when I have to do this in a workspace is I'll create a user parameter manually with the same name as the resource parameter and keep it unpublished. Then I can use it anywhere I need within the workspace without the transformers or readers/writers throwing up warnings or errors about the missing parameter. If the path that the resource is pointing to is directly accessible from my own machine, I'll also set the default value for the parameter within Workbench to point to that location so that I can run the workspace before publishing it up to FME Form.

 

image

Reply


Community Stats

30,162
Posts
114,482
Replies
37,809
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.