Creation of a field fails when a field name is longer than 30 characters and the field name matches an existing field with some additional prefix text - Known Error

Creation of a field fails when a field name is longer than 30 characters and the field name matches an existing field with some additional prefix text Description When a field name is longer than 30 characters, an alias for the field needs to be used due to limits on the maximum column name allowed in the backend database. It appears during creation that internally an attempt is made to shorten the alias by removing any initial prefix text up to a first '_'.

For example if there is a field called 'applicants_nationality' (len=22) and a new field 'external_applicants_nationality' (len=31) is added, it appears that the 'external_' is stripped, and a check made to see if there is a match for 'applicants_nationality' which finds the existing field.

If the there is a match then an info message "Column name ' ' already exists". The sys_dictionary record is created, but the field is not added to the database table and no storage alias is created.

Steps to Reproduce

1. Create a standalone table 2. Create a String field with the label "Field 1" and set the column name to 'applicants_nationality'. 3. Note the field's label is correctly displayed. 4. Create a String field with the label "Field 2" and override the column name to be 'external_applicants_nationality'. 5. Save/Submit.

The second field's creation will create the sys_dictionary record, but showing the info message in the UI: "Column name 'external_applicants_nationality' already exists". Note the field label for 'applicants_nationality' now appears blank. The field does not exist and has not been created correctly, and the column label for the first field will appear to be blank.

Workaround This problem has no workaround and is currently under review. To receive notifications when more information becomes available, subscribe to this Known Error article by clicking the Subscribe button at the top right of this form.

If a field name is greater than 30 characters in length, and if the leading characters up to and including the first '_' would leave a name that matches an existing storage alias which would trigger this problem, then extend the name by adding one or more characters so that the remaining name will not match.