Custom Fields: FAQ

Go to System Settings > Objects and Fields, select the object, click Object Fields, then New Field. Full steps: Custom Fields Guide, Creating a field.

In the CRM: Contacts, Events, Leads, Opportunities, Opportunity Projects, Organizations, Price Book Entries, Products, Projects, Quotes, Quote Products, Tasks, and Custom Objects. See Where custom fields can be created for Marketing and Service.

No, you cannot change the field type after a custom field has been created. Create a new custom field with the correct field type instead, then bulk update your records through importing.

No. You can create a custom field that is similar to the standard field, then update it to fit your specific needs.

Yes. Cloning copies the field’s configuration, not the values in it. See Cloning a field to another object.

Every value in it, on every record, is deleted permanently, and any rules, actions, or filters that reference the field stop working. If you only want it out of the way, the Hidden setting on the field hides it without deleting its values. See Deleting a field.

Yes. Check Sort values alphabetically on the field, which applies everywhere the values appear. See Field types.

Only if the fields are mapped first, under System Settings > Opportunity Conversion. See Mapping fields from opportunities to projects.

Yes. Create the fields before you import so they are available to map. See Importing Data Guide.

Per standard object: 2 on Free, 50 on Plus, 100 on Professional, 200 on Enterprise. Per custom object: 100 on Professional, 500 on Enterprise. Enterprise plans can create up to 25 multi-line text fields per object. See Limits by plan.

A Text field holds up to 255 characters; a Multi-Line Text field holds up to 4,000. See Field types.

A field shows on a record only once it has been added to that object’s Page Layout. See Page Layouts.

In the Page Layout editor, hover over the field and click its gear icon. See Page Layouts.

Yes. Check Read-only in the field’s settings. See Anatomy of a field.

With field-level permissions, which need the Enterprise plan and Advanced Permissions. Restrictions apply to record layouts, list views, and reports. See Field-level permissions.

Yes, with a field dependency. It works for dropdown fields only, not multi-select dropdowns. See Field dependencies.

An Enterprise field that aggregates one field from a related list into a field on the parent record. See Roll up Summary field.

The accepted file types are PNG, JPG, and JPEG. The maximum file size is 5 MB. If a file doesn’t load correctly, try adjusting the pixels or dimensions; typically 1600w x 1200h pixels will work. Images displayed in records are resized to 320w x 200h, so some larger or higher resolution files may not save.

No.

Yes, they count towards your data storage limits. They do not count towards your record count limits, however.