Understanding Custom Component Fields

Custom Component Fields can look like an option for storing extra data, but they are not meant for general use. This article explains what these fields are, why they exist, and what to use instead so you can avoid future issues with reporting, integrations, and system stability.

Custom Component Fields

Custom Component Fields are typically reserved for use in integrations and automations where data needs to connect in a tightly controlled way.

Because of this, Custom Component Fields are not supported for general client configuration. Using them in the wrong way can cause problems with data visibility, reporting accuracy, or compatibility with future Bullhorn updates.

Recommended Alternative: Custom Objects

If you need a way to capture additional information in Bullhorn ATS, the supported option is to create a Custom Object.

Custom Objects allow you:

Enhance Bullhorn by adding modules to your records.
Capture data that is not standard to the out-of-the-box workflow.

For more details, see Custom Object.