Skip to main content
  • EN

I have a workbench that creates a table based on a number of joins that are on occasion, filtered on an attribute. Instead of manually entering the attribute values, I’d to read a list of attributes from, say, an Excel doc e.g. NSG001, NSO001, TES001 so I don’t have lots of duplicated transformers. How do I iterate through a list of values and plug them into FeatureJoiners without duplicating lots of stuff.

 

Hi ​@howeitzor I would suggest creating a new workbench using a workspace runner to call a modified version of this workbench. In the new workbench you will read the excel “list” and the workspace runner will call the workbench to run once for each value in the excel list.

Test Batch Processing Method 3: Using the WorkspaceRunner – FME Support Center

Hope that helps!

Hi ​@howeitzor I would suggest creating a new workbench using a workspace runner to call a modified version of this workbench. In the new workbench you will read the excel “list” and the workspace runner will call the workbench to run once for each value in the excel list.

Test Batch Processing Method 3: Using the WorkspaceRunner – FME Support Center

Hope that helps!

Thanks ​@crutledge. This looks promising. I’ve setup the workspace runner. Assuming I create a user param in the joining workspace then set it to be the read name from the Excel doc, is it possible to then use that in the joining workspace in an attribute filter? I can’t seem to use it.

EDIT: I replaced the AttributeFilter with a TestFilter and looks promising.

Hi ​@howeitzor 

The way I had understood it was the excel was a “list of things to loop through”. In the past I have read in an excel sheet to provide a list of variables to pass as parameters to the second “child” workspace. In the pic below I read in an excel sheet with paths and imagery index names. Then those two get passed to the workspace runner. For each line in the spreadsheet the second workbench is called and does it’s thing.
 

Does that help? Did I understand correctly?

Hi ​@howeitzor 

The way I had understood it was the excel was a “list of things to loop through”. In the past I have read in an excel sheet to provide a list of variables to pass as parameters to the second “child” workspace. In the pic below I read in an excel sheet with paths and imagery index names. Then those two get passed to the workspace runner. For each line in the spreadsheet the second workbench is called and does it’s thing.
 

Does that help? Did I understand correctly?

Exactly. My workspace runner just finished and everything looks good. Appreciate the help, thanks again.

Community Stats

31,788
Posts
120,757
Replies
39,405
Members

Latest FME

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.