Solved

fme workspace reading wrong parameter

  • 14 December 2018
  • 9 replies
  • 1 view
Y

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

icon

Best answer by david_r 14 December 2018, 16:47

View original

9 replies

david_r
Rank
Userlevel 4

Can you post a minimal working example here?

Y

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.

david_r
Rank
Userlevel 4

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.

Y

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

david_r
Rank
Userlevel 4

using fme 2017.0

Just tried with FME 2017.1, no problems... Consider recreating the parameter.

Y

Just tried with FME 2017.1, no problems... Consider recreating the parameter.

I try recreating as suggested same issue. keep reading Node

Y

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.

david_r
Rank
Userlevel 4

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"

 

Y

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.

Reply


Community Stats

28,716
Posts
109,493
Replies
36,561
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.