Editions Available: Corporate;Enterprise Audience: Administrative Users

How to Use and Edit Field Mappings

Overview

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 if you want to:

  • Add a new field (like a dropdown or picker) to a specific record type—such as Company, Job, or Candidate
  • Add, remove, or rename options in a dropdown (EX:, Candidate Status, Industry, Skills, Specialties)
  • Make a field required or optional on an Add/Edit form
  • Move a field to a different section or change who can see it (EX: make an internal field visible to all users)
  • Rename field labels that display on the form
  • Control how a field behaves (EX: default values, picker rules, or multi-select behavior)
  • Map or copy field values between record types (e.g., Candidate to Contact)
  • Sync company or client data between different areas of Bullhorn
  • Fix a field that isn’t saving or showing data correctly when records are updated
  • Restore dropdown values that were removed but still exist on older records
  • Align field visibility and behavior across entity tracks (EX: Placement, Vacancy, Opportunity)
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

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

Your mapping changes should now be visible.

FAQs

Q: I have a SQL error stating that the data must be truncated to fit for a field mapping I am looking at. How can I find out what the maximum character limit is for a field mapping?

A: There are 3 ways to view character limits. Not every single field will have a clearly defined character limit in the resources listed below. If you are unsure, you can always test the fields manually.

  1. 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.
  2. Go into Admin and find the corresponding field mapping. Click on the pop up link and view the character limit.
  3. 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.

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:

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

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.