All docs pages (49)

Field Creator

Create several custom fields on one object in a single run, grant each one field-level security, and add them to the page layouts you pick.

Updated 2026-11-09

Field Creator creates custom fields from a form in one run. It can also grant field-level security (FLS) on permission sets and profiles and add the fields to page layouts. Open Metadata → Field Creator. The page notes that you need Customize Application, plus permission to manage profiles and permission sets for FLS.

How to use it

  1. 1 · Object: pick the object.
  2. 2 · Add a field: fill in Label, API name and Type, then click Add field. The API name comes from the label (characters other than letters and digits become underscores; a leading digit gets an X in front), and you can type your own. The full name, such as Account.Score__c, shows next to the button. The types are Text, TextArea, LongTextArea, Number, Currency, Percent, Checkbox, Date, DateTime, Email, Phone, Url, Picklist and Multipicklist. Depending on the type you also get Length, Precision, Scale, Default, Checked by default, Required and Picklist values (one per line). Description and Help text are optional.
  3. 3 · Fields to create lists what you added, with a trash icon to remove one.
  4. 4 · Field-level security (optional): expand a field and tick its Permission sets and Profiles. Tick Also grant Edit for read and edit; otherwise access is read-only. Apply these targets to all fields copies one field's choices to the rest. A field with no targets gets no FLS on any permission set or profile.
  5. 5 · Page layouts (optional): tick Layouts. Under Target section per layout, keep Auto — last field section or pick a section. Tick Place as read-only to add the fields read-only.
  6. Click Create N fields.

Add field checks the field first: the API name must start with a letter and use only letters, digits and underscores, scale can't exceed precision, and a picklist needs a value.

What you see

The result panel shows "Result — N created, M failed" and one row per field: created, or Salesforce's error. Then an FLS line, such as "Granted field-level security on 6 rows across 2 fields", with the failure count and first error if rows failed. Then one line per layout: fields added and fields already present, or the error.

Created fields leave the list; failed ones stay so you can fix them.

What it reads and writes

It reads the object list, permission sets (PermissionSet where IsOwnedByProfile = false), the permission sets behind profiles, and the object's page layouts (Tooling API).

Clicking Create writes right away; there is no confirm step.

  1. Fields: each field is created on its own through the Tooling API (CustomField), so one failure doesn't stop the others.
  2. FLS: for the created fields only, one FieldPermissions record per field and target is inserted through the REST API, in batches of 200. Read is always granted; Edit only if you ticked it.
  3. Layouts: each chosen layout's metadata is read, fields not already on it are added to the target section, and the layout is saved back through the Tooling API. Required fields are placed as required; others as read-only or editable, following Place as read-only. One layout failing doesn't stop the others.

There is no undo: created fields stay until you delete them in Setup.

Saved defaults: Text length 255; LongTextArea length 32,768 with 3 visible lines; Number, Currency and Percent precision 18, scale 0. A Text default is saved as a text value. Checkbox is always saved with a default (checked or not). Picklist and Multipicklist are restricted, keep your order and have no default value.

Limits

  • Only the 14 types above. Lookup, master-detail, formula, roll-up summary, auto-number, rich text and other types are not offered.
  • In version 1.1.13 the Default box shown for Number, Currency and Percent is not saved; only a Text default is. In the release after 1.1.13 a number default is saved.
  • Lengths and precision aren't checked against Salesforce's maximums; Salesforce's error shows in that field's result.
  • A picklist value containing a semicolon is split into two values.
  • The list keeps its fields when you switch objects, but the layouts shown are always the current object's. Create one object's fields at a time.
  • In version 1.1.13, adding fields to page layouts writes them under their full name (Account.Score__c), while a layout names its fields without the object (Score__c), so the fields may not be placed correctly. Check the layouts afterwards, or add the fields in Setup. Fixed in the release after 1.1.13.