Using special characters
The fields that are a part of the logical key for any record (such as OrganizationCode and OrderNo) have some restrictions. For such fields, the application does not support the use of special characters listed in the following table.
| Special Character | Description |
|---|---|
| & | Ampersand |
| > | Greater Than |
| < | Less Than |
| % | Percent |
| " | Quotation Mark |
| + | Plus sign |
| ' | Single quotation or Apostrophe |
| ( | Parenthesis |
| ) | Parenthesis |
| [ | Square Bracket |
| ] | Square Bracket |
Note: You can use the plus (+) and ampersand (&)
signs only in the ItemID field.
Note: A forward slash (/) must not be used in attributes that form
part of a path in another attribute. For example, Category ID must
not include a forward slash, as Category ID is used to form the attribute
Category Path, which uses the forward slash as a path separator.
In addition,IBM® recommends against using third-party vendors' reserved special characters. For example, in certain situations, data with underscore characters ("_") on an Oracle database could result in unexpectedly slow query performance because the database deciphers the underscore as a single character wildcard.
The following fields have no restrictions and support all characters:
- All description fields (for example, item description)
- All name fields (for example, organization name)
- All address fields (for example, billing address) Note: However when creating address fields through the UI, the information entered after the quotation mark (") is truncated and appears as a new entry in YFS_PERSON_INFO table. To work around this problem, use apostrophe (') instead of quotations.
- All instruction fields (for example, gift wrapping)
- All text fields (for example, reasons and comments)
Note: Any mobile device does not support the use of the ampersand
(&) character.