Issue with a!toJson function

RE: Issue with a!toJson function

Richard Michaelis — Fri, 17 Mar 2023 17:59:08 GMT

nice idea

RE: Issue with a!toJson function

Mike Schmitt — Fri, 17 Mar 2023 17:55:48 GMT

The first thing i'd try is to pre-sanitize it so that a!toJson() treats the newlines like newlines:

a!toJson(
  value: {
    test: {
      assuranceText: substitute(ri!input, "\n", char(10))
    }
  },
  removenulloremptyfields: true()
)

RE: Issue with a!toJson function

manikumarc0208 — Fri, 17 Mar 2023 17:51:03 GMT

Hi Mike, the idea is in a json string we want to send "\n" in between the text so that other systems (built on different technology) will interpret it as new line and show the message with line breaks. so wanted to know how get the output from toJson("\n") as "\n" instead of "\\n"

RE: Issue with a!toJson function

Richard Michaelis — Fri, 17 Mar 2023 17:40:05 GMT

ah you mean backslash.
yeah i toJson will just convert the text you provide.
So try to write the text with the line breaks according to appian reals instead of taking a JSON command and convert it to a JSON statement -> appian is not prepared to do that in my mind -> a string is expected. plain convertion.
char(10) should perhaps to the trick?

RE: Issue with a!toJson function

Mike Schmitt — Fri, 17 Mar 2023 17:36:33 GMT

Your input doesn't have "newline characters" as far as a!toJson() is concerned, it just has the text "\n". So when you call a!toJson() on your original string, it's escaping your "\n" characters to "\\n", because it has no way of knowing you don't want it to preserve those as plaintext.

RE: Issue with a!toJson function

manikumarc0208 — Fri, 17 Mar 2023 17:32:14 GMT

here I am expecting \n\n but in the output i am getting \\n\\n

RE: Issue with a!toJson function

manikumarc0208 — Fri, 17 Mar 2023 17:31:22 GMT

RE: Issue with a!toJson function

Richard Michaelis — Fri, 17 Mar 2023 17:28:12 GMT

Hi Manikumar,
can you mark the word you think is extra?