How to Use and Edit Field Mappings

If you're looking to update which fields appear when adding or editing records in Bullhorn Whether you are looking to change field layouts, rename dropdowns, control visibility by role, or setting default values, Field Maps is where you do it. This guide walks you through how to use and edit field mappings to customize 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 Maps

You might need to use or edit Field Maps 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. You can also control who sees a field by adjusting its visibility.
Customize field layout: Rearrange fields by moving them to a different section or renaming 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.

Best Practices: The above updates help you ensure your forms stay aligned with your workflow, maintain clean data, and offer the right fields to the right users.

Field Mappings Details

In Field Maps, click on the field name to find the number of characters allowed in the field. It is listed under Text Field Limit.

Use Field Maps to update how fields behave, appear, or are required when users add or edit records.

You access Field Mappings from the Bullhorn menu.

From your Bullhorn Menu, select Admin > Field Mappings.

As an administrator, you use Field Mappings to control the location and behavior of fields that display on the Add & Edit pages of your records, such as:

The name of the field.
The order in which the fields appear (and whether or not they appear at all).
Whether or not the field is required to complete.
If the field is a drop-down or picker, the values that appear within that field, if there is a default value, and how many values a user can select at once.
Brand new fields that you create.
Defined opportunity, job, and placement tracks.

Each set of field mappings is broken down by entity. For example, to change the values that appear within the Status drop-down on the contact record, expand the Contact entity and locate the Status field. If necessary, you can use the column headers as filters.

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

How to Edit Field Mappings

Log into Bullhorn and navigate to Menu > Admin > Field Mappings.
Select the entity you wish to edit and complete any required changes.
Select Save at the top of the page.
Log out of and then back into Bullhorn.

Your mapping changes should now be visible.

Troubleshooting

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 a SQL 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 three ways:

Log in as the user, go to field mappings and click on the hyperlinked field mapping name. The popup box has the character limit listed.
Go into Admin and find the corresponding field mapping. Click on the pop up link and view the character limit.
Visit the developer documentation and go to References > Entities 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)

See the attached screen shots if you are unsure.

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 radio button 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.

FAQs

Q: What fields are enabled for mass update by the Mass Update Candidate Database Field entitlement?

A: To test this, all I did was turn on the entitlement and then turn it off and compared the drop down. When the entitlement is enabled you gain: "Change Category, Change Skills, Change Industry, Change Source"" - Ryan Nicholson

Q: What should I do if the address is missing from job records?

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

Fast Find for the affected Corp in Admin.
Open Field Maps for the client's Private Label.
Expand Job tracks and filter for fullAddress.
Unhide the fullAddress and change the Sort Order so that it is the same as the address field
Click Save

Q: Why is my field missing?

A: 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:

Go to Bullhorn Menu > Admin > Field Mappings.
Select the entity(ies) where the field was configured.
Verify setup on all available tracks.
If missing from the master track, add the field.
Check for and resolve any sort order clashes (sort orders must be unique).
Click Save.
Log out and back in to confirm the changes.

Q: Why isn’t my mapped field syncing with payroll or an integration?

A: 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.

What You’re Actually Doing

Field Maps are a behind-the-scenes tool that shape how users interact with Bullhorn. By editing Field Maps, you're managing the structure and behavior of your forms across Bullhorn. This includes:

Customizing the layout and behavior of forms across your ATS
Tailoring visibility and access to fields based on user roles
Enforcing data quality through required fields and dropdown control
Supporting team-specific workflows by aligning fields with your processes

Ensuring consistency and clarity across all record types and tracks

Outcome: Whether you're adjusting one field or restructuring entire forms, Field Maps allow you to adapt Bullhorn to fit the way your team works.