Smartstaff, administrator
687
edits
Changes
no edit summary
New custom field naming restrictions have been introduced in order to promote good naming practices. While this may seem restrictive right now, the benefits over time will include the reduction of configuration errors, e.g. accidental trailing spaces, the reduction of system errors and complexity, e.g. handling cases for reserved characters in the variable processor, and an improvement to system performance. The new field naming restrictions will only apply to new fields, or an attempt to change the name of an existing field.
You will only be able to update a field's name if the new name is limited to the English alphabetalphanumberic, e.g. a-z/A-Z, numbers, e.g. and 0-9, and dashes or underscores, e.g. '-'/'_'. Please note that other special characters and blank spaces will no longer be allowed in a field name.
<!--38463 - Strict Custom Field Guidelines-->
