Map Fields for Work Plans
Learn how standard fields for work plans are mapped from templates and how to map custom fields.
Required Editions
| Available in: Lightning Experience |
| The Field Service core features, managed package, and mobile app are available in Enterprise, Unlimited, and Developer Editions. |
| User Permissions Needed | |
|---|---|
| To customize work plans custom field mapping: | Customize Application |
Standard fields for work plan templates, work step templates, and work plan template entries are automatically mapped to work plans and work steps. The mapping of these fields can’t be changed. The standard fields that are mapped from work plan templates to work plans are Name, Description, and Execution Order. The fields that are mapped from work step templates and work plan template entries to work steps are Action Definition, Action Type, Description, Execution Order, Name, and Work Plan Execution Order.
You can also add custom fields to work plan templates, work step templates, and work plan template entries so that your workers have all the information they need to efficiently and accurately complete their work. You can then map which fields to copy from the templates to a work plan or work step record.
- Add custom fields to the work plan template / work step template / work plan template entry and to the work plan / work step.
-
From Setup, in the Quick Find box, enter Work Plans. On the Custom
Field Mapping card in Work Plans Settings, select which custom field values to include from
templates in work plans and work steps. You can:
- Map custom fields from work plan templates to work plans.
- Map custom fields from work step templates and work plan template entries to work steps.
Note You can’t delete a custom field mapped to a work plan or a work step. -
Save your work. When work plans are generated, the custom fields are copied from the
templates to the work plan and work steps of a work order or work order line item.
In the Field Service mobile app, custom fields that take numerical inputs show plus and minus buttons only if the custom field name starts with Quantity. All other custom fields that take numerical inputs show a text box.
- Guidelines for Mapping Custom Fields for Work Plans
Learn the best practices for mapping custom fields from templates to work plans and work steps. Mapping custom fields helps your front-line workers retain important information that they use to complete their work.
Guidelines for Mapping Custom Fields for Work Plans
Learn the best practices for mapping custom fields from templates to work plans and work steps. Mapping custom fields helps your front-line workers retain important information that they use to complete their work.
- Map any of these field types to custom fields of the same data type.
- Formula
- Auto Number
- Checkbox
- Currency
- Date
- Date / Time
- Geolocation
- Number
- Percent
- Phone
- Picklist
- Multi-select Picklist
- Text
- Text Area
- Text Area (Long)
- Text Area (Rich)
- Text (Encrypted)
- Time
- URL
- Each target field can have one source field mapped to it.
- You can map Auto Number fields to field types Text or Text Area.
- You can map Text and Text Area fields to custom field types of Text, Text Area, Text Area (Long), and Picklist. If you map to a Picklist field, the picklist must be unrestricted.
- You can map custom Picklist fields to custom field types of Text, Text Area, and Picklist (unrestricted), but not Text Area (Long).
- When mapping between Picklist and Text fields, if the source field value is longer than the target field allows, your data truncates.
- You can map custom lookup fields to custom lookup fields pointing to the same object.
- When mapping source entity custom fields (Work Plan Templates / Work Step Templates / Work Plan Template Entries), the selected target entity custom field (Work Plan / Work Step) must be of equal or greater length.
- You can’t delete mapped custom fields from the source entity or the target entity. To delete a field, remove its mapping first.
- You can’t change the field type of a mapped field. To change a field’s type, remove its mapping first.
- You can’t uninstall a package that references fields included in Work Plans Custom Field Mapping. Before uninstalling the package, remove any mappings of referenced fields.
- When mapping custom number, currency, or percent fields, the target field must have the same length and number of decimal places.
- Don’t map custom formula fields to other formula fields or any other type of field.

