Not all UTF-8 characters are supported across every part of the platform. Some characters are fully restricted; others may appear to work but can cause unexpected behaviour. This article describes where restrictions apply.
General Guidance
Combining characters (also called decomposed characters) modify another character - for example, characters combined with accent marks or composite Unicode characters such as emoji modifiers. These should only be used within object record data. They must not be used in system names, unique key attributes, or usernames. Where possible, use the precomposed Unicode version of a character instead.
Emoji behave similarly to combining characters. They should not be used in configuration fields and must not be used in unique key attributes.
Usernames
Main user interface - the following characters cannot be used in usernames:
=|combining characters
OData access - when usernames are used for OData access, the following additional characters cannot be used:
?^{}/|
Object and Attribute Definitions
System Names must use only A–Z, 0–9, and _, and must not begin with a number. Other characters may appear to work but can lead to system errors.
Business Names must not contain:
\(backslash)'(single quotation mark)
Object Records
In referenced object identifiers, do not use:
\::(two adjacent colons)
These can break reference links and cause navigation errors.
Screen Filters
Using ^ in a screen filter will cause the search to return no results.
Process Definitions
Process Names must not contain:
''(two adjacent single quotes)::(two adjacent colons)?^_/
Process parameters must not begin with a number.
Process filters - % is always treated as a wildcard. Using ^ will cause the filter to return no results.
Sender, receiver, subject, and attachment names must not contain:
''::|\^space characters
carriage returns
Sender addresses must not contain " (double quotation mark) and must use standard 7-bit ASCII characters only.
Attachment names - the following characters will be removed automatically from attachment names:
?><
The character / cannot be used in attachment names at all.
Design Recommendations
Use simple alphanumeric characters and underscores in system names and identifiers. Avoid special characters in configuration names wherever possible, and test integrations such as OData and email if non-standard characters are required.