Convert Rich Text to Long Text and remove HTML tags

I have a rich text field called Notes.

When a user exports the data table to CSV, I’d prefer the plain text version (e.g. remove all HTML tags) of the Notes field as the output.

To try and solve this, I created a form record rule that sets a separate Notes (Long Text) field to the form value of Notes.

However, I’m finding this approach still retains the HTML tags.

Is there a better way to strip out the HTML tags in a rich text field so a plain text version is available in the CSV export?

1 Like

Great idea!

We’ll add this in the coming days to the Text Utilities pipe.

1 Like

Awesome, thanks Moe! Looking forward to using it.


I see the team has added 3 new methods in the “Tadabase Text Utilities” pipe where you can convert:

  • HTML to Text
  • HTML to Markdown
  • Markdown to HTML

Let me know if you have any questions.


Thanks for the update, @moe!

Just tested out and the HTML to Text method works well with text containing bold or italics.

It does not appear to work when the value contains any of the following in the rich text editor:

  • Text style (Paragraph, Heading 1, etc.)
  • Underline
  • Strikethrough
  • Custom text color
  • Custom background color
  • Text align (left, center, right)
  • Bullet list
  • Numbered list
  • Horizontal line
  • Table
  • Insert link

Might this be a bug in how the pipe functions?

Thanks for the feedback. I’ll get this checked out and update you again very soon.

@moe @ScottG
I think Underline, Strikethrough can not use in markdown valid format.
officially style(css) not supported in markdown.
Markdown only support tags like:

  • Heading tags [‘h1’, ‘h2’, ‘h3’, ‘h4’, ‘h5’, ‘h6’]
  • Blockquote Tag [‘blockquote’]
  • Paregraph and Block tags [“p”, “div”]
  • Table tags [‘table’, ‘tr’, ‘th’, ‘td’, ‘thead’, ‘tbody’, ‘tfoot’, ‘colgroup’, ‘col’, ‘caption’]
  • Image tag [‘img’]
  • Link tag [‘a’]
  • List Item tag [‘ol’, ‘ul’, ‘li’]
  • Emphasis tag [‘em’, ‘i’, ‘strong’, ‘b’]
  • HorizontalRule Tag [‘hr’]
  • Hard Break Tag [‘br’]
  • Code Tag [‘code’]
  • Preformatted tag [‘pre’]

i have tested with Tadabase pipe and it generate nice output

	<!-- Paragraph and Heading tags -->
	<h1 style="text-align: center;">This is a Heading 1</h1>
	<p style="text-align: justify;">This is a paragraph. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut a massa quis risus viverra egestas. Integer bibendum, nulla sed varius volutpat, quam justo sollicitudin turpis, nec eleifend mauris purus vel nisl. Nullam id orci ac augue congue iaculis nec vel nulla. Praesent vestibulum augue eget urna ultrices, et tincidunt ipsum luctus. Duis laoreet tincidunt diam, sit amet bibendum libero pharetra vel.</p>
	<!-- Underline and Strikethrough -->
	<p><u>This text is underlined.</u></p>
	<p><s>This text has a strikethrough.</s></p>
	<p><b>This text has a bold.</b></p>
	<p><i>This text has a italic.</i></p>
	<!-- Custom text and background colors -->
	<p>This text has a custom color and background color.</p>
	<!-- Text alignment -->
	<p style="text-align: center;">This text is centered.</p>
	<p style="text-align: right;">This text is right-aligned.</p>
	<!-- Bullet and Numbered lists -->
		<li>Item 1</li>
		<li>Item 2</li>
		<li>Item 3</li>
		<li>Item 1</li>
		<li>Item 2</li>
		<li>Item 3</li>
	<!-- Horizontal line -->
	<!-- Table -->
	<table style="width:100%">
	    <th>Header 1</th>
	    <th>Header 2</th>
	    <th>Header 3</th>
	    <td>Row 1, Column 1</td>
	    <td>Row 1, Column 2</td>
	    <td>Row 1, Column 3</td>
	    <td>Row 2, Column 1</td>
	    <td>Row 2, Column 2</td>
	    <td>Row 2, Column 3</td>
	<!-- Link -->
	<p>Visit <a href=""></a> for more information.</p>


Hi @christopher93, thanks for your reply. I still seem to be running into issues.

Below is my test of the HTML to Text method in the Tadabase Text Utilities pipe.

The source code I’m using as input is as follows:

<p>these are some test notes</p>
<p><strong>bold</strong> and <span style="text-decoration: underline;">underline</span></p>
<p>with a few:</p>
<li>bullet points</li>

cc @moe

I see the issue here, we’ll have this fixed soon hopefully. It comes down to the double quotes you’re using that are breaking the JSON payload.

We’ll need to find a better solution for this.

If you test with this, it will work:

<p>these are some test notes</p> <p><strong>bold</strong> and <span style='text-decoration: underline;'>underline</span></p> <p>with a few:</p> <ul> <li>bullet points</li> </ul>
1 Like

@ScottG this is now fixed.

1 Like

Hi @moe , thanks for the update. Confirming this is now working when testing the pipe directly on the Pipe page in the App Builder.

I’ve implemented a form rule when creating/editing a record to run the Notes rich text value through the pipe and return the pipe response into a new Notes (text) field, but this doesn’t appear to be updating the new field on the back end. I’ve also tried using a table rule instead of a form rule - same result.

Any thoughts on what might be happening here? Thanks so much!

@ScottG when you can, would you mind testing it again?

Hi @moe, thanks for the quick turnaround. It appears the pipe is now fixed to handle underlines and strikethroughs, but the bulleted/numbered lists and line breaks are causing the table rule not to run.

I don’t understand!

Using this code:

<p>these are some test notes</p> <p><strong>bold</strong> and <span style='text-decoration: underline;'>underline</span></p> <p>with a few:</p> <ul> <li>bullet points</li> </ul>

will give me this in the Rich Text Field:

I test it in the pipe, it gives me this:

but when I use it:

It gave me this:

Can anyone help me please.

I want to create a Message template where I can Automatically add record whenever I create User account and keeping its format.

When I create a User Account: I am adding a record rule to add a Message Template under that account.

The problem is that, it always turns like this:

I hope someone can help me please.

Thank you

Hey any idea why on the Tadabase Text Utilities HTML to Text, this works…


Im migrating a load of HTML to Text so I can better control it in CSS and I found a lot of failed conversions and on troubleshooting it I weeded it down to this issue.