BambooHR Custom Tables Do Not Appear in Okta
Last Updated:
Okta Integration Network
All Engines
Okta Classic Engine
Okta Identity Engine
Overview
BambooHR custom tables do not appear in Okta because the integration only supports pulling custom fields, standard fields, and standard tables as attributes. To resolve this, convert the data entries from custom tables to custom fields in BambooHR. Administrators observe that custom tables created in BambooHR fail to populate in Okta and remain unavailable for attribute mapping.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- BambooHR
- Provisioning
- Attribute Mapping
- Custom Tables
Cause
This is a known limitation of the Okta integration with BambooHR.
Solution
Why do BambooHR custom tables fail to appear in Okta?
The Okta integration with BambooHR only pulls custom fields, standard fields, and standard tables as attributes. Okta does not support pulling custom tables.
How is the BambooHR custom table limitation resolved?
Implement the workaround by converting the data entries in BambooHR and contacting support for additional assistance.
- Convert the data entries in BambooHR from custom tables to custom fields.
- Contact BambooHR Support for additional details regarding data conversion.
