-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Affects Version/s: 5.4.6, 5.8.0
-
Component/s: Assets - Import
-
1
-
Severity 3 - Minor
-
4
Issue Summary
This is reproducible on Data Center: (yes)
When using the Object Schema Import type, to import objects from one schema / instance to another - any TextArea Attributes are imported as plain text, and not rich text, so the target will show the attribute content with HTML tags.
Using CSV export from source>import to target - the text is imported correctly.
Steps to Reproduce
- Create an object schema x with an object type x which has a TextArea Attribute
- Create at least one object (e.g. Obj1) in object type x populating the TextArea attribute (possibly with some formatting, otherwise - we'll only see the pragraph tabs <p></p>)
- Create a new object schema y, and set up an Object schema import type (Object Schema>Configure>Import) to import from Schema x
- At the end of the import configuration, create a predefined structure and configuration.
- Enable all object type maps and the import - and synchronize the import
- Compare the object imported (Obj1) between source and target.
Expected Results
The textArea attribute contains the same values, e.g:
this is a test
source is TextArea
Actual Results
Source:
this is a test
source is TextArea
Target (Imported):
<p>this is a test</p><p>source is TextArea</p>
Workaround
Two workarounds possible:
1.Map the TextArea attribute to a text attribute (e.g. TempText), and set up an automation rule:
WHEN: Object Updated/Created
IF: objectType=myObjectType
THEN: set Attribute Value: the attribute MyTextArea will be set with the value: ${TempText}
The Text attribute will be set into the Textarea attribute and all formatting (HTML tags) will be respected!
2. Use a CSV to import/update objects from one Schema to another - as using REGEX will not be able to clear all HTML tags coming from the source