Converting a string to an integer array

RE: Converting a string to an integer array

PhilB — Wed, 31 Aug 2016 16:40:00 GMT

Ok - that's why you've seen the behaviour that you have. Putting 4;7;10 in a text rule input on the interface designer will not produce an array of three integers; it simply returns a string 6 characters long. I can see why you might expect this, though, as that's similar to the /designer behaviour when adding multiple values to a constant of type list of text.

If you try with a rule input that is text multiple and add each the values you mention above separately, the earlier examples that use tointeger() will work just fine as you're then passing it a list of string rather than a single string.

RE: Converting a string to an integer array

judym598 — Wed, 31 Aug 2016 16:33:19 GMT

text - not text multiple

RE: Converting a string to an integer array

PhilB — Wed, 31 Aug 2016 13:33:39 GMT

Judy - out of interest, in your test was your rule input text, or text multiple?

RE: Converting a string to an integer array

Colton Beck — Tue, 30 Aug 2016 20:32:51 GMT

Happy I could help!

RE: Converting a string to an integer array

judym598 — Tue, 30 Aug 2016 20:31:50 GMT

Yes! That worked! Thank you!!!

RE: Converting a string to an integer array

Colton Beck — Tue, 30 Aug 2016 20:28:25 GMT

Interesting.

Would something like this work for you?:
tointeger(split("1;2;3",";"))

RE: Converting a string to an integer array

gaurava322 — Tue, 30 Aug 2016 20:26:33 GMT

Hi Judy, try touniformstring(), coltonb is correct..

RE: Converting a string to an integer array

judym598 — Tue, 30 Aug 2016 20:23:40 GMT

That works but it doesn't work when I replace the {1,2,3,4} with my pv which is (4;7;10). Create a rule input (i.e., dataType of type 'Text' and enter 4;7;10 as the test value) with the rule input =tointeger(touniformstring(ri!dataType)). When tested - the result is 4710 not 4;7;10

RE: Converting a string to an integer array

Colton Beck — Tue, 30 Aug 2016 20:16:02 GMT

It may appear that way, but tostring() does not preserve inputs as multiple.

To test, plug these into the expression editor to see the difference:
tointeger(tostring({1,2,3,4}))
tointeger(touniformstring({1,2,3,4}))

RE: Converting a string to an integer array

judym598 — Tue, 30 Aug 2016 20:05:38 GMT

The 'tostring(pv!dataTypes_int)' part works just fine. The semicolons are saved there - my problem is when I convert it back to an integer.

RE: Converting a string to an integer array

Colton Beck — Tue, 30 Aug 2016 20:03:10 GMT

Instead of using tostring() to convert to text, you could try touniformstring() which should maintain the array.