Skip to main content
Best Answer

Batch Run a workspace failing with feature type as a parameter

  • July 16, 2019
  • 4 replies
  • 65 views

Forum|alt.badge.img

I have a workspace that uses a feature reader to read just one table from a geodatabase. I need to batch run this workspace for every feature type in the geodatabase.

I created a new workspace with a schema reader and a workspace runner to run the original workspace, with the feature type populated from the fme_feature_type_name from the schema reader. The feature reader in the child workspace fails.

If I hard code the feature type in the published parameter in the workspace runner in the parent workspace, the feature reader in the child workspace runs. But as I need to batch run this doesn't solve my problem.

I've made a pair of sample workspaces that replicate this issue with an Excel Spreadsheet. They're here:

 

Is there any way to do a batch run with a feature type as a parameter that can be varied to cover the whole schema?

 

 

Best answer by itay

Hi @ella_s,

You can add a ParameterFetcher transformer in the child workspace to grab the parameters values and add them to attributes and then use them in the FeatureReader.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

chrisatsafe
Contributor
Forum|alt.badge.img+2
  • Contributor
  • July 19, 2019

Hi @ella_s,

If you leave the Feature Types to Read parameter blank inside the WorkspaceRunner it should read all three (Sheet1, MySheet, and AnotherSheet).


Forum|alt.badge.img
  • Author
  • July 22, 2019

Hi @ella_s,

If you leave the Feature Types to Read parameter blank inside the WorkspaceRunner it should read all three (Sheet1, MySheet, and AnotherSheet).

Hi @chrisatsafe, thanks for the response but that doesn't solve my problem. I've inherited a complicated child workspace that needs batch running and unfortunately it really does need to be ran one geodatabase table at a time, otherwise I wouldn't need the parent workspace at all.


itay
Supporter
Forum|alt.badge.img+18
  • Supporter
  • Best Answer
  • July 22, 2019

Hi @ella_s,

You can add a ParameterFetcher transformer in the child workspace to grab the parameters values and add them to attributes and then use them in the FeatureReader.


Forum|alt.badge.img
  • Author
  • July 26, 2019

Hi @ella_s,

You can add a ParameterFetcher transformer in the child workspace to grab the parameters values and add them to attributes and then use them in the FeatureReader.

Thanks @itay that worked for me. Another workaround I've been told about is to create a new published parameter as a text field.