Different Result Forms for Similar iPaaS Expressions
I was testing a flow in iPaaS recently and found that if I set a property value by selecting a row in a data model array using the Find In expression, the result was an integer, however, if I set the same property using the Get In expression with the same condition and attribute, the result was the same value but treated as text.
In short, the output for the first option with the data model and Find In expression was:
"request_specs_attrID": 3153
And the output for the second option with the Get In expression was:
"request_specs_attrID": "3153"
I can add a Text as Numbers expression around it to convert it, but I wanted to check if this was the expected behavior or a bug.
Answers (2)
Hi Corrine,
I think our folks would need to know the flow you are working on to better be able to offer advice. Can you provide that flow's name?
Sincerely,
Mark Sayers
Sr Support Consultant, CS
You can try doing this though:
--On the property where you're storing the result of the get in expression, click the three vertical dots to the left of the property
--Go to Attributes
--Change the Data Type to "Integer"
This tells the property to store the result of the "get in" expression as an integer specifically.
Like this:
in this screenshot, "ID (general)", which is a normal property, yields "1234"
(a string)
but "ID (integer)", which is a property where you set the data type to Integer, using the instructions above, yields 1234
(a number)