Which connector?:

Hibob

Additional details:

The HiBob connector currently syncs custom-table definitions — table and field metadata (CUSTOM_TABLE / CUSTOM_TABLE_COLUMN) — but not the employee-level values held in those tables.

HiBob's API exposes this data via GET /people/custom-tables/{employee-id}/{custom-table-id} ("Read all entries of the given custom table"); the connector currently only calls the metadata endpoint, never this entries endpoint.

Fivetran support confirmed this is a current connector limitation, not a configuration issue or something resolvable on the HiBob side, and recommended a feature request as the path forward.

In our HiBob instance this affects 21 custom tables and 123 fields — the definition lands, the value never does. This blocks employee-level reporting for roughly 150 fields in our internal People-analytics field catalog, spanning compensation, benefits, and compliance data.

Requested change:
Extend the HiBob connector to also call GET /people/custom-tables/{employee-id}/{custom-table-id} per employee/custom-table pair, so row-level entry values sync into the destination alongside the existing table/field definitions.

Impact if resolved: Unblocks employee-level self-serve reporting across ~21 custom tables / ~150 fields that are currently visible only as empty schema in the warehouse.