Forum Discussion
Formatting bug w. "Multiple lines of text" (Rich text)
I am curious to know whether it's a bug or not and if anyone else is experiencing the same thing? The column is set to be formatted as "Rich Text". When users edit the column and save, the form view ignores all line breaks for the column. Same thing goes for the list view (DescPlain is just for comparison with a column with "Plain Text" formatting).
List View:
Form View:
On top of that. When a user edits the item once again, the line breaks return, but now we see that special characters, like ":", has been replaced with what looks like some kind of html encoding ":".
Anyone got an idea about how to fix this?
- Yes, this is a bug that MS needs to fix. Those are supposed to be colons (:) but are html/rich text encoded representations of them.
- Darn! Follow up question: The line breaks, that is being ignored in th list view + display form. Is that also a bug or by design?
Hanne_Lauritzen Are you trying to apply JSON formatting to "Multi-Line Text column with enhanced rich text" column?
Also, as per the below Microsoft official documentation, JSON formatting for "Multi-Line Text column with enhanced rich text" is not supported officially (at least the documentation is not updated if it is a new feature):
Documentation: Use column formatting to customize SharePoint
Please click Mark as Best Response & Like if my post helped you to solve your issue. This will help others to find the correct solution easily. It also closes the item. If the post was useful in other ways, please consider giving it Like.
ganeshsanap Nope. No json here. It is the display form (which we have no json control over) as well as in the list view (without any formatting) that is giving me this issue. Just to add, I am aware that Enhanced Rich Text is not supported in json formatting, but this is Rich Text (not Enhanced).
I get the error in my own environment as well as on my customer's domain, so it's definitely something in Microsofts end.I am trying to figure out if this is a known bug or expected behaviour, so that we can make a decision on how to move forward; If it's a known bug, I am leaning towards waiting for a fix. If they made some behavioral changes to the field type, then we need to figure out what to do as the changes has pretty big consequences for a solution with a large description field. The customer won't implement Enhanced Rich Text, since it is more cumbersome to edit, so that is unfortunately not a viable solution for them.
