Change node value issue

[fogmajor]

Hello and Good evening
I have a change node with 6 items
I pass it a string "10" and change the output to Input 1 triggered
I pass it a string "20" and change the output to Input 2 triggered
I pass it "100" and it gets confused it should display Input 10 triggered
Does the change node not look for absolute values?

Thank you in anticipation
Andrew

[Steve-Mcl]

Hi, it is quite unclear what you are doing from the text description.

Can you please create a demo flow, export it (select the nodes, press CTRL-E, copy to clipboard) and post it here. Include inject nodes with the values (rather than some external data source we have no access to)

See this post for how to post a flow - How to share code or flow json

[Buckskin]

"100" is not "10", try 'contains 10'

[fogmajor]

I have visited this forum on multiple occasions and found it to be rude and very up its own A***
If you cannot understand what I am saying from the text question I am at a loss for words
A change node cannot deal with a with a 10 value or a 100 value and treats them as the same

[Steve-Mcl]

@fogmajor

found it to be rude and very up its own A***

I'm sorry you feel that way. I certainly wasn't being rude and I did politely ask "Can you please create a demo flow". This would help me understand your issue better (so I could help).

[Colin]

Or at least show us how you have configured the Change node.

[jbudd]

Hello Andrew

@fogmajor

Does the change node not look for absolute values?

I think it does look for absolute values, but after transforming "100" to "Input 10 triggered", it moves to the next comparison where the payload still matches "10".

Have you considered regex or jsonata in your change node?

A regular expression can distinguish between "10" and "100" by specifying the start and end of the string eg ^100$

As for jsonata you can convert the input string to a number, divide it by 10 and concatenate with string prefix and suffix.

If you need a worked example to experiment with, let me know.