You are viewing limited content. For full access, please sign in.

Question

Question

Store Rich Text as Plain Text for reporting purposes

asked on September 26, 2019

We are using a Form with several Rich Text fields, and storing the variables from the Form in a SQL database for reporting purposes.  While the rich text is great for the Form itself and for the user experience, when it gets captured as a variable in Workflow it's full of HTML tags, which is obviously not great for readability.

 

Does anyone have any ideas on how I could strip out the HTML elements so that they don't appear in our reports?  We are using version 10.4

 

Example:

 

Becomes:

There was a thing that happened that was worthy of an incident report.&nbsp; Here are some bullet points to illustrate my meaning:<p></p> <div><ul><li>Point A</li><li>Point B, which is not much different than Point A</li></ul><div><br></div></div><div><b>This statement is in bold</b></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px"><div><i>This statement is in italics, <u>and indented</u></i></div></blockquote>

0 0

Answer

SELECTED ANSWER
replied on September 26, 2019

You can use token formatting to convert them to plain text. See the help file for more info.

2 0
replied on December 31, 2019

Are there any specific instructions for this?  I also would like to store the plain text version of the rich text field to a SQL database.  I cannot find instructions related to this in the linked help files.

0 0
replied on December 31, 2019

I should have brought up before, but it was brought to my attention that most of the formatting options provided by the rich text field in Laserfiche Forms can be handled by the SQL reporting service.  I think, by trial and error, the only one I found that didn't carry over was the indentation.  So even though it's not very reader-friendly when viewing it directly in the DB, the reports still come out pretty good.

 

Hopefully this helps.

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.