Once an object exists, you can change its name, icon, description, color, default record template, and its list of properties. Some changes are safe; others have downstream consequences worth understanding.
Renaming
Renaming an object is safe. The id (obj_...) does not change, so all Views, Records, and Workflows continue to work. The new name appears in every surface within seconds.
Adding / removing properties
- Adding a property is always safe. Existing records simply show an empty value for the new property until it’s filled in.
- Removing a property deletes its stored values at the same time. Workflows or formulas that reference the property will no longer resolve it.
Removing a property is not a “hide”. The values stored against it are deleted, not retained. Hide the property from views instead if you only want to declutter the interface.
Changing a property’s type
Changing a property’s type updates the property definition and re-indexes it for search. Existing stored values are not automatically converted to the new type. Values that don’t make sense for the new type may render blank until re-entered. Test the change on a small set of records first.
Deleting
Deleting an object removes it from navigation. System objects (such as Tasks) cannot be deleted or renamed.
See also
