Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Incorrect format of CSV coming for Rich Text Editor properties

SA-32586

Summary



Developer has used properties having Rich Editor Control in their application.

The property get stored in DB accordingly.

Now, when user is trying to extract data from database via
Business Intelligence Exchange (BIX) and populating them as a CSV file, they noticed that all the Rich Text Editor values are appearing in incorrect format. It is corrupting the entire CSV file.

Error Messages



Tags are being included in the csv file generated after extraction.

Steps to Reproduce



1. Create a property of type single value and add a Rich Text Editor control into that.
2. Add that property into
BIX extract rule.
3. Run your application and put some values into that Rich Text Editor area.
4. Now, execute the Bix Extract into CSV format. The CSV file would come up in a wrong format containing all HTML tags.


Root Cause



BIX is used for the extraction of rich text properties which is beyond the scope of BIX.

Resolution



The main purpose of BIX is to extract the data not to transform it.

BIX does not support extraction from rich text properties, because the extraction of rich properties includes transformation or modification of data.

Published January 31, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us