I have created a report to pull historical data on custom fields that their format is Rich text. I was advised that:
"What happens normally when you set those fields to be tracked is that it will post the updates in the update stream and it can reference the text of the field at that time to be able to display it in the report. Rich Text is one of the only exceptions to this. Normally you can use the "Old Text Value" and "New Text Value" fields like you have, but Rich Text is stored in an HTML format in order to maintain the formatting that is being used.
Because of this, though the update stream can show that updates were made, the journal entry report doesn't have a native field in it that can pull and display that HTML text. It's a rare scenario, I think this only the second time I've seen this in the last 2 years or so.
In this case the only way you would be able to go about tracking changes in a report like this would be if you were to create a new field, probably a paragraph text field, so that the text can actually be referenced by the report."
Unfortunately, I cannot just disregard the already created Rich text format custom fields and replace them with Text fields as there are data populated in them within the system. Is there a way to create a calculated custom field that pulls data from the Rich text format fields and converts them to text, or change the report code in a way that I can convert the rich text value to text so that the report shows the data, or perhaps a function that converts Rich text to text?
Solved! Go to Solution.
Views
Replies
Total Likes
This is an interesting one and definitely a valid ask. Seems like an oversight from WF that when they introduced the rich text field option, they didn't also make it to be able to pull into things like you're mentioning. My first thought was to add a text format calculated field in the form that simply references the rich text field (so the only calculation is DE:[name of rich text field]) so you could pull that field into a report but it keeps giving an error that it's not valid, it doesn't allow you to do it with rich text fields.
Have you asked support about this? If this isn't in the works, I'd post an Idea for it - let me know when you do and I'll upvote it!
This is an interesting one and definitely a valid ask. Seems like an oversight from WF that when they introduced the rich text field option, they didn't also make it to be able to pull into things like you're mentioning. My first thought was to add a text format calculated field in the form that simply references the rich text field (so the only calculation is DE:[name of rich text field]) so you could pull that field into a report but it keeps giving an error that it's not valid, it doesn't allow you to do it with rich text fields.
Have you asked support about this? If this isn't in the works, I'd post an Idea for it - let me know when you do and I'll upvote it!
Madalyn, Thank you very much for taking the time to read my post and to test it and comment on it; I really appreciate it.
The support confirmed that the report does not work for Rich Text, even through the report can be created. I entered this as an Idea in Experience League.
No problem. I've voted on the Idea!
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies