Resource Search Field Mappings

When you create a resource search field using the Configure Resource Search Fields page, you can map a custom resource request field to the contact field. This is so that the resource search filter field is populated automatically with the value from the resource request, and resources can be filtered out if they do not match the value. These mappings are used by auto-staffing, Resource Request Staffer, and by the Resourcing tab on a resource request.

For example, let's assume your contact records have a custom checkbox named Passport Holder which indicates if the person has a passport. You want to be able to filter by this custom checkbox, so you create a resource search field for it named Has Passport.

When a resource request involves travel abroad, you select a custom checkbox named Passport Required on the resource request.

So you map the resource request's Passport Required field to the contact's Passport Holder field:

This means that when you staff a resource request that has the Passport Required checkbox selected, the Has Passport resource search filter field is selected automatically, and resources who do not have the Passport Holder checkbox selected are filtered out.

Note:

You cannot map to formula fields on the Contact object. This means that when filtering by resource search fields for formula fields, their filter values are not populated automatically.

Mapping Rules

Please note the following before you configure mappings:

• Mapped fields must be of the same field type.
• Mapped number fields must have the same maximum length, and the same maximum number of decimal places.

• When matching using Resource Request Staffer, only mapped fields of the following field types are supported:

  • Checkbox
  • Currency
  • Date
  • Lookup Relationship
  • Number
  • Percent
  • Picklist (not the Multi-Select type)
  • Text

  Mapped fields of other field types, such as Geolocation, are not considered by Resource Request Staffer.

Tip:

If you want to be able to filter by a custom field that can have two values such as "yes" and "no" but can also be set to null to indicate "no preference", you must create the field as a picklist on both the Contact and Resource Request objects, then create a mapping between them. Do not create the custom field as a checkbox because once a checkbox has been set to true or false, it cannot be set to null so you will not be able to pass the "no preference" value to the filter.

Mapping to Fields on Related Records

You can map a resource search field to a field on a record related to the resource request by following one or more lookup fields. When you open the Source Field on Resource Request drop-down on the Configure Resource Search Fields page, lookup fields display with a trailing >. When you select one of these options, the drop-down displays the fields on the related record, including any further lookups. If you select a lookup field, the path continues. If you select any other field, it is set as the source for the mapping. The drop-down displays your full selected path, separated by >. For example: Project > Account > Industry.

When you edit an existing resource search field, the Source Field on Resource Request drop-down is pre-populated with the saved path. To make changes, you can delete a lookup field in the path to navigate to a different branch or clear the path entirely.

Managed Mappings

The following table lists the managed mappings that are available for resource search:

Managed Mappings for Resource Search

Resource Request Field	Contact Field
Resource Role	Resource Role
Start Date	Start Date
End Date	Last Date
Region	Region
Practice	Practice
Group	Group