With a few exceptions (noted when applicable), the names of Oracle Commerce properties and dimensions used in EQL requests must be in an NCName format.

(This restriction does not apply to the names of non-root dimension values or to the names of search interfaces.) The names are also case sensitive when used in EQL requests.

The NCName format is defined in the W3C document Namespaces in XML 1.0 (Second Edition), located at this URL: http://www.w3.org/TR/REC-xml-names/#NT-NCName

As defined in the W3C document, an NCName must start with either a letter or an underscore (but keep in mind that the W3C definition of Letter includes many non-Latin characters). If the name has more than one character, it must be followed by any combination of letters, digits, periods, dashes, underscores, combining characters, and extenders. (See the W3C document for definitions of combining characters and extenders.) The NCName cannot have colons or white space.

Take care when creating property names in Developer Studio, because that tool allows you to create names that do not follow the NCName rules. For example, you can create property names that begin with digits and contain colons and white space. Any names which do not comply with NCName formatting will generate a warning when running your pipeline.

The property must also be explicitly enabled for use with record filters (not required for record search queries). Dimension values are automatically enabled for use in record filtering expressions, and therefore do not require any special configuration.