I have a template that I call and run with parameters but one of the parameters can be like this "something - else", but it only read "something", I need the whole word. any ideas?
Thanks
Solved
fme workspace reading wrong parameter
Best answer by david_r
If you're using the command line to pass the parameter value, that is an important detail. If you pass parameters that contains spaces or certain special characters, you should always put double quotes around them, e.g.
fme.exe --BoundaryType "Node - MUX"
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.
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.
Can you post a minimal working example here?
the issue is with boundary type. it only read Node and forget about the rest. I try using in the definition Type : Text multiline and same result, wrong.
- 8391 replies
That's a funny one. I did a quick test but was unable to reproduce the issue using FME 2018.1.
Please try the attached template:
parameter_test.fmwt
I've had some experiences where parameter definitions have been corrupted, meaning that they've started to behave unexpectedly. In those cases I've had luck deleting the parameter and recreating it.
That's a funny one. I did a quick test but was unable to reproduce the issue using FME 2018.1.
Please try the attached template:
parameter_test.fmwt
I've had some experiences where parameter definitions have been corrupted, meaning that they've started to behave unexpectedly. In those cases I've had luck deleting the parameter and recreating it.
using fme 2017.0
- 8391 replies
using fme 2017.0
Just tried with FME 2017.1, no problems... Consider recreating the parameter.
Just tried with FME 2017.1, no problems... Consider recreating the parameter.
I try recreating as suggested same issue. keep reading Node
Just tried with FME 2017.1, no problems... Consider recreating the parameter.
when I run the template from inside fme it works ok reads Node - MUX, but when I send a request and run fme from command line it only read Node.
- 8391 replies
- Best Answer
If you're using the command line to pass the parameter value, that is an important detail. If you pass parameters that contains spaces or certain special characters, you should always put double quotes around them, e.g.
fme.exe --BoundaryType "Node - MUX"
If you're using the command line to pass the parameter value, that is an important detail. If you pass parameters that contains spaces or certain special characters, you should always put double quotes around them, e.g.
fme.exe --BoundaryType "Node - MUX"
thank you so much, that was the problem, I wasn't using double quotes.