Skip to main content
Solved

Workspace Runner not Writing to Excel

  • July 10, 2019
  • 2 replies
  • 61 views

I have a parent bench that uses a workspace runner to run a child workbench several times using different source shapefiles. The parent and child workbench's run with no errors but when I check the file directory the child bench has not written anything!

This is reflected in the child workbench log which states that the expected number of features have been read but non have been written.

Does anyone know why this is happening? The child bench runs fine and writes as expected when run manually.

Best answer by earl359

@markatsafe you were right! The shapefile reader in my workbench wasn't set to read different feature types and so didn't read-in anything after the first shapefile. I just had to tick 'merge feature type' in the reader parameters and it worked fine. I hadn't come across this issue before as normally I would just change the reader source file manually.

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.

2 replies

Forum|alt.badge.img+2

@earl359 if you can, can you include a minimum working example so that reproduces the issue so contributors can try and help. The most likely cause is a bad parameter being passed form the parent to child workspace.


  • Author
  • Best Answer
  • July 12, 2019

@markatsafe you were right! The shapefile reader in my workbench wasn't set to read different feature types and so didn't read-in anything after the first shapefile. I just had to tick 'merge feature type' in the reader parameters and it worked fine. I hadn't come across this issue before as normally I would just change the reader source file manually.