|
Administrative Help
Editing Custom Fields
|
Important: Editing custom fields can have significant impact on existing data associated with that field, including loss of existing data .
- New fields—If you add a custom field to an existing application and define a default for that field, existing records (items) from that application will not include the default value for the field. The only exception to this is if the new field is a calculated field. Calculated fields are populated through all existing applicable items.
- Custom field types—You can change field type if you are changing to a similar field type. For more information, see
- Custom pick lists
- Changing types—You can change a single-select pick list to a multi-select list. You cannot change a multi-select list to a single-select list.
- Editing—When you edit custom pick list options (change an existing field option), any records using that option are updated with the change. For details on configuring pick lists, see Configuring Custom Pick Lists.
- Deleting—When you delete a custom pick list option, the option is deleted from any records using the option. If the pick list is a multi-select list, any unchanged options are not impacted.
- Custom status fields
- Editing—When you edit custom status field options (change an existing option), any records using that option are updated with the change.
- Deleting—When you delete a custom status field option, the option is deleted from any records using the option.
- Changing field names—You can rename a custom field but any reports that include the field will not run correctly until they are edited in Report Studio to correct the field name.
The report will fail with an Expression parsing error: "The query contains a reference to at least one object '[Presentation].[<application>].[<original field name>]"