Field Mappings

Field Mappings are an admin tool that shape how users interact with Bullhorn. By editing Field Mappings, you're managing the structure and behavior of your forms for records like Candidates, Contacts, Jobs, and Placements.

When changing fields, use custom fields instead of reusing existing ones. Changing fields can break how the system works, disrupt workflows, or cause problems with reports and integrations.

Common Reasons to Use or Edit Field Mappings

You might need to use or edit Field Mappings to:

  • Add or modify fields: Add a new custom field or manage options within existing ones, such as adding, removing, or renaming dropdown values (e.g., Candidate Status, Industry).

  • Control field behavior and visibility: Define field properties like default values, multi-select behavior, or set them as required or optional on forms.

  • Customize field layout: Rearrange fields by changing their order, or rename their labels on a form to align with your team's workflow.

  • Manage data and integrations: Map or copy field values between different record types (e.g., Candidate to Contact) and ensure consistent data syncing for integrations or payroll systems.

  • Troubleshoot field issues: Resolve problems with fields that aren't saving correctly or are displaying incorrect or missing data.

Access Field Mappings

Only Admin users with the proper entitlements can use Field Mappings. Access Field Mappings from the Bullhorn menu by selecting Admin >  Field Mappings. If your company has multiple private labels, use the Private Label picker to choose the private label you want to edit.

Understand the Field Mappings Page

Each set of field mappings is broken down by entity. The entity panel groups entities into sections: Entities, Tracks, Lists, Change Requests, and Custom Objects. To find an entity, type its name in the search box and select it to view its fields.

For example, to change the values that appear within the Status drop-down on the Contact record, select the Contact entity and locate the Status field.

The field grid has the following columns: Field, Hidden, Label, Edit Type, Required, Allow Multiple Values, Sort Order, Last Modified, and Last Modified By. Fields are sorted by sort order.

Sort and Filter Fields

Use sorting and filtering to find fields quickly.

  • Sort: Select a column header to sort the column in ascending or descending order.

  • Filter: Filter by Field, Label, Edit Type, or Last Modified By. You can combine multiple filters. Clear individual filters, or clear all filters at once.

Your unsaved edits remain in place while you sort and filter.

Refresh the Field List

After you save changes on a field's edit page, click Refresh on the Field Mappings page to see the updates there.

Edit Field Mappings

You can edit Hidden, Label, Required, Allow Multiple Values, and Sort Order inline in the grid. Expand a row to edit Description, Value List, Display List, Default Value, and Hint.

  1. Go to Menu > Admin > Field Mappings.

  2. Select the entity you wish to edit and complete any required changes. You can switch to another entity without losing your work.

    • Entities with unsaved changes show an edit pencil icon.

    • Changed cells are highlighted.

    • A counter shows your total unsaved changes.

  3. When ready, click Save. The Save button saves your changes across all the entities you edited, including custom objects.

Your changes apply automatically. They can take about a minute to appear for other users.

If you have unsaved changes, Bullhorn asks you to confirm before you refresh, switch private labels, or close the page. If a change can't be saved, nothing is saved, your edits remain on the page, and a message explains what to fix.

Edit a Single Field on Its Own Page

To edit all the settings for one field, click the pencil icon on the field. The edit page opens in a new tab. The top of the page shows the entity, private label, column name, field limits, and when the field was last changed and by whom. Sort Order is validated before you save, and you'll see "Enter a whole number" if the value isn't valid.

Locked Settings

Hover over a locked setting to see why you can't change it. For example, you can only select the Allow Multiple Values checkbox if the field supports multiple values.

Because all records (except for companies) must have owners in Bullhorn, the Owner field must always be required. If you un-select the Required checkbox for an Owner field and then attempt to create and and save a record without an owner, you'll see an error message.

Troubleshooting Field Mappings

If you encounter issues with field mappings, use the following tips to diagnose and resolve common problems.

Data Truncation and Character Limits

If you receive an error stating that data must be truncated, it means the text you're trying to save exceeds the field's character limit. You can check the limit in two ways:

  1. Go to Field Mappings and select the pencil icon on the field. The top of the field's edit page lists the field limits.
  2. Visit the Entity Reference Guide in the developer documentation and navigate to your desired entity. Open the entity and find the corresponding field mapping. In the column Type you will see a number in parenthesis that indicates the limit (i.e String (100) means 100 character limit).

Field Won't Save or Appears Blank

If your field won't save or the data disappears after you save, it may be a character limit issue. The CustomText field has a limit of 100 characters. For longer text, you must use the CustomTextBlock field type, which has no character limit.

Incorrect or Missing Data

If your field is blank or showing the wrong data, use the following list to troubleshoot.

  • Hidden Field: First, ensure the field is not hidden. Go to Menu > Admin > Field Mappings and confirm the Hidden setting for your field is off.

  • Repurposed Fields: If you're seeing unexpected data, a field may have been repurposed. This can cause legacy data to reappear. Always use custom fields for new data.

  • Value Lists: Updates to a value list or display value list only affect new records created after the change. Older records may still display values that have since been removed from the list.

  • Field Syncing: If a mapped field isn't syncing with a payroll or other integration, the field type in Bullhorn ATS may not match the required field type in the destination system. Verify that the field types align to ensure a proper sync.

  • Candidate Mappings: If candidate field mappings are incorrect, verify that the Source, Value List, and Display Value List match exactly. Review the field settings under Menu > Admin > Field Mappings for the candidate entity.

Address Missing from Job Records

If you're unable to find the address field when adding a job, despite it being unhidden in Field Mappings, follow the steps below:

  1. Go to Menu > Admin > Field Mappings.
  2. Select the Job entity and use the Field filter to find fullAddress.
  3. Unhide the fullAddress and change the Sort Order so that it is the same as the address field.
  4. Repeat this for each Job track (Job II, III, and IV).
  5. Click Save.

Field Missing from Job, Opportunity, or Placement Record

This usually happens when the field is not properly configured on the entity master track or if there are sort order conflicts. While information may save initially, it can disappear when clicking the Edit tab.

To fix this:

  1. Go to Menu > Admin > Field Mappings.

  2. Select the entity where the field was configured.

  3. Verify setup on all available tracks.

  4. If missing from the master track, add the field.

  5. Check for and resolve any sort order clashes (sort orders must be unique).

  6. Click Save.

Mapped field not syncing with payroll or another integration

This usually occurs when the field type in ATS doesn’t match the field type in the sync destination. Verify that the field types align. If the issue continues, contact Support for assistance.