Skip to main content

BambooHR Fields Available in Lattice

The following are available attributes for mapping between BambooHR and Lattice. For Compensation standard fields, read HRIS Attribute Opt...

A
Written by Adam Kroboth

The following are available attributes for mapping between BambooHR and Lattice. For Compensation standard fields, read HRIS Attribute Options for Auto-Syncing to Lattice Compensation.

Standard field in Lattice

Field in BambooHR (by default)

Can map BambooHR custom field?

External User ID

EEID

Note: This is different from the "Employee Number" field in BambooHR profiles. See here for more information.

No

Name

Personal > Name

No

Preferred name

Personal > Name

Only pulled upon creation.

No

Email Address

Personal > Contact > Work Email

No

Job Title

Job > Job Information table > Job title

No

Status

Status

No

Department

Job > Job Information table > Department

No

Manager

Job > Job Information table > Reports To

Yes

field type: Employee

Phone Number

none

No

Start Date

Job > Hire Date

Yes

field type: Date field

Birth Date

Personal > Birth Date

Yes

field type: Date field

Ethnicity

none

Yes

field type: List

Gender

Personal > Gender

Yes

field type: List

Sexual Orientation

none

No

Job Architecture (JA) fields

Job Architecture (JA) fields

Job Architecture (JA) fields

Job Type

none

Yes

field type: List

Job Function

none

Yes

field type:List

Job Level

none

Yes

field type: List

BambooHR Fields available to link to Lattice

These are BambooHR fields that we can manually link to Lattice - User attributes page.

BambooHR Default fields

  • Division

  • EEO

  • Ethnicity

  • Location

  • Original Hire Date

  • Termination Date

  • PayType

  • PayGroup

  • Nationality

BambooHR Custom fields

Note: Calculated fields can not be used for the Bamboo integration.

Field types:

  • List (maps to Lattice dropdown/multiple choice)

  • number (maps to number)

  • date (maps to standard fields that are date type - Start Date and Birthday)

  • pay_type (maps to Lattice dropdown/multiple choice)

  • Custom Tabular fields that are Effective Dated - the field types that can be mapped follow the same rules as above.

Did this answer your question?