Skip to main content
  • EN

In my workflow I have a main process which executes other workspace runners and passes published parameters of the main process to the workspace runners. One of these parameters is a text separated by comma (student_list) and when it is passed to the workspace runner is not getting interpreted as a text, but as multiple parameters.

This is the main workflow: 

When Student_List is passed to the workspace:

StudentElegibilityProcess: {C:/Program Files/FME/fme} G:/Git/compass-fme/student-eligibility/student-eligibility.fmw --ScenarioGuid *** --OrgGuid *** --DbServer *** --DbName *** --DbUserName ** --DbPassword *** --AuditFile {G:\Git\compass-fme\student-eligibility//audit_eligibility.json} --ALLOWS_OUT_OF_BOUNDARY_TRANSPORTATION true --SOLVE_CLOSEST_FACILITY_BATCH_SIZE 100 --STUDENT_LIST 000157141 --000170660 000171155 --ZonesUrl http://*** --HazardZonesUrl http://**r 2>@1

Have you tried embedding the student list in double quotes: "00157141, 00170660, 00171155" ?

Have you tried embedding the student list in double quotes: "00157141, 00170660, 00171155" ?

yes, it doesn't work
yes, it doesn't work
Then submit this to support@safe.com as it seems to be not the right way to handle these parameters.

 

 

This is a known bug, you can work around it be re-defining the published parameter in the child workspace from "Text" to "Text (multiline)". That should let you pass comma-separated values.

This is a known bug, you can work around it be re-defining the published parameter in the child workspace from "Text" to "Text (multiline)". That should let you pass comma-separated values.

It's doing the same even with Text (multiline)

 

 

It's doing the same even with Text (multiline)

 

 

Which version of FME are you using?

You should also take a look at this thread: https://knowledge.safe.com/questions/43868/how-to-pass-comma-separated-values-in-work-space-r.html

Which version of FME are you using?
2017.0.1.1 Build 17291 win64

 

 

Hi @rrdlpl, I'm sorry for the inconvenience experienced here!

I tested in 2017.0 Build 17291 and I was able to reproduce this behaviour. However, when testing with 2017.1 Build 17521 the values were passed through as expected without issue.

I haven't identified the specific fix that changed this behaviour, but I encourage you to test with the latest FME 2017.1 Beta to ensure your workflow operates as expected in the newer version.

safe.com/beta

 

 

Additional thanks to @david_r and @erik_jan for their support here! 🙂

Reply


Community Stats

30,177
Posts
114,556
Replies
37,844
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.