Text Custom Attribute Constraints
- As a general rule, special
reserved XML characters, such as apostrophes, ampersands, and greater-than and
less-than symbols (,&,’,%,<,>), cannot be used in text custom
attributes.
- To work around this constraint, these reserved characters can be “escaped” or contained within a CDATA section.
- Here is an example of an escaped ampersand (&) character: &
- Special reserved XML characters such as apostrophes, ampersands, and greater-than, less-than symbols can pass without being escaped by turning off the XML validation for text that is contained with the CDATA brackets.
- Your IT professionals can help you apply these techniques.
- When importing text custom attributes, the maximum length is 1,000 characters.
- If the text length is more than 2,000 characters, the transaction file import fails with the following reason: “Incorrect file format”
- When a reference tag for a text custom attribute is included in an email, the rendered text that is inserted into the email includes only the first 1,000 characters.
- Input for text custom attributes in the user interface of the customer portal is 1,000 characters.
- Text custom attribute values exported as part of the shopper export only include the first 100 characters.
- A given text custom attribute should be populated either through the import or through CRMS user interface, but not both, because the last used method might overwrite the file.
Copyright © Cloud Software Group, Inc. All rights reserved.