Apr 24, 2020 10:14 AM
According to this support article, it says that we can use markdown formatting in any “long text field with rich text formatting on”.
However, this doesn’t work.
We have a long text field with rich text formatting on, but when we add markdown syntax into our text, nothing happens.
For example, if we type the following into our long text field:
**test** *test* test
We would expect the results to look like:
test test test
(Notice that the 1st word is in bold, the 2nd word is in italics, and the 3rd word is plain text. That’s what we would expect.)
But everything just stays in plain text, and looks like:
**test** *test* test
Thoughts on how to get this markdown formatting to work within a rich text long text field?
Apr 24, 2020 11:33 PM
Thanks for researching this so thoroughly! :slightly_smiling_face: Do you know how we can report this as a bug to Airtable?
May 07, 2020 11:43 PM
As @kuovonne said, half of the fields are working, half are not.
This is a particiular problem as I was hoping to finally replace my old URL fields with markdown,
In theory this should take 10 seconds, copy the URL column, paste it into notepad, add [Link] and then wrap the link in
The problem is, pasting [Link](http://www.example.com) into the rich field doens’t actually turn it into a link, it interprates it as raw text.
I was hoping maybe it was doing something similar to TinyMCE, and you could paste actual A HREF links into the field, but it strips all tags and pastes as plain text, so that doesn’t work either.
Anyway, I’m sure they’re aware of it and working on it.
May 09, 2020 12:19 PM
Correct. This is a suboptimal mess.
To actually use a long text field as a pretty link field, you have to:
[CNN][1]\n http://cnn.com[1]: \n
May 09, 2020 01:57 PM
There are three ways to create pretty links in rich text fields:
An ugly workaround if you have to bulk insert several records at once is to put the markdown text in a plain long text field, and then use the scripting block to copy the text to an rich-text field.
May 21, 2020 04:14 PM
It’s a bug. Their document lists the markdowns that are not working currently.