I'm a little confused about what you mean by "must" support. |
I mean that the Marketo textarea/SFDC longtext must support embedded line breaks. Otherwise, it could not hold data that contains line breaks, which it does (you can post such data directly from a form textarea, for example).
A second question is whether flow rules as saved in your Marketo instance can have line breaks. This, too, is supported.
The part that's broken is that the widget in the Marketo UI that is used to manage flow rules is a one-line textbox that does not support embedded line breaks. They are removed even before the data is sent to your instance.
That's why the hack has to skip the rules applied by the textbox display widget, since those are stricter than the rules of the underlying database(s) -- a pattern found somewhere in almost every web app. (If and when flows can be updated via API there would be no reason to reproduce this display rule.)
If you do a change data value that uses "\n", it will not show a line break when you view the lead record. |
That's because the escaped character "\n" never gets unescaped. It's a literal "slash-followed-by-lowercase-n" in that context. demo
So by adding a literal "slash-n" you aren't even trying to add a line break.
The fact remains, though, that even if you do put (programmatically) a true line break the textbox, it will also get stripped by default. So you need to go a level deeper.
In general, I'd advise against adopting flows that require such "hacks" |
Sure, but if you want it now, you have to use a hack.
Adchoices