Hi @InfaReQt,
After few tests, the problematic part of your formula seems to be substitute({BodyText}, "\n", "%0A")
Looking at this post, I found this sentence from Christoph:
It’s not exactly the same case, but I think the problem is related. To get rid of this issue, you will have to replace this part of your formula with
substitute({BodyText}, "
", "%0A")`
The character between the two first double quotes being a new line character. The format you’ll have to use for your BodyText column actually depends on the type of the column:
- if BodyText is a Long text column, you don’t have to do anything special, the line breaks in the Long text editor will be correctly replaced. However, other special formatting (bold, italic, etc.) won’t be rendered as you might expect (you’ll actually see the markdown formatting in your event description such as **Lorem Ipsum** instead of Lorem Ipsum
- if BodyText is a text column, you will have to insert new line characters in your text field, as discussed in the recent thread Insert a new-line into a (short) text field?. If you define the content of the BodyText column yourself (and you alone), you can also decide to replace the \n new line symbol by a special less problematic character you never use anywhere else in your message such as ¤ and adapt the substitute formula consequently
PS: I noticed that your formula contains &location=`: either you forgot to specify a location, or you can get rid of this part as it doesn’t contains any information.
Hope this helps!
Bests,
Benjamin
