So, found out that when using Cloverleaf 5.7 this isn’t an issue. Testing in this environment with the string map function works as expected.
What I had to eventually do was change the encoding on the outbound thread to ISO-8859-1 in conjunction with the string map call.
I opened a ticket with Infor and this was what they said:
“Beginning with 5.8 we merged the regular cloverleaf with the multi-byte cloverleaf which is probably why you see the difference and need to specify the encoding for it to handle properly.”
Author
Replies
Viewing 0 reply threads
The forum ‘Cloverleaf’ is closed to new topics and replies.