OpenWindow Parameter Value
-
- Posts: 38
- Joined: March 16th, 2022, 1:04 pm
- Contact:
OpenWindow Parameter Value
I am passing a parameter GDTXKY into an OpenWindow service. A typical value for this parameter looks like '12345|CL|1.000'. The value being passed does not seem to handle the '|' symbol correctly.
- Attachments
word count: 34
-
- Posts: 38
- Joined: March 16th, 2022, 1:04 pm
- Contact:
Re: OpenWindow Parameter Value
Update I tried a fix where I pass in the values needed to create the key as two separate strings and add the special character later and this as the result. The two string should be '191356' and 'CL'.
The results showed everything but the capital L. To test if the 'L' was causing the issue, I passed just the letter 'L' as the string value and no value was passed to the widget. I thought it was the '|' symbol but turns out it doesn't like the 'L'?
The results showed everything but the capital L. To test if the 'L' was causing the issue, I passed just the letter 'L' as the string value and no value was passed to the widget. I thought it was the '|' symbol but turns out it doesn't like the 'L'?
- Attachments
word count: 89
-
- Posts: 329
- Joined: August 26th, 2021, 9:18 am
- Contact:
-
- Posts: 38
- Joined: March 16th, 2022, 1:04 pm
- Contact:
Re: OpenWindow Parameter Value
I think I remember someone mentioning a change being made in regards to this issue. Instead of it breaking after a specific character now, the last character in the string gets lost.
The current work-around I have in place is to append ".00" to the parameter before it is passed to the the widget and then user subtring-before({paramvalue},'.') to convert it back to the right format.
The current work-around I have in place is to append ".00" to the parameter before it is passed to the the widget and then user subtring-before({paramvalue},'.') to convert it back to the right format.
word count: 69