BambooHR Custom Fields Not Pulling

Connector Questions & Issues
1

Is this your first time deploying Airbyte: No
OS Version / Instance: EC2 t2.large
Memory / Disk: 16Gb
Deployment: Docker
Airbyte Version: 39.16-alpha
Source name/version: 0.2.0
Destination name/version: Snowflake 0.4.24
Step: n/a
Description:
Trying to figure out how to use the BambooHR custom reports stream. I have a custom field in BambooHR called Squad, which I have access to via my API key. I’m able to see this field on the front end. However when I input this field as squad into the Airbyte Web UI. I’ve tried every iteration of squad (see image below)

image
image741×176 16.6 KB

Unfortuantely the data still comes up as all NULL

image
image800×556 10.3 KB

However, on the front end almost all users have the Squad field filled in
image

2

Hi @kyle-cheung,
Could you please share your sync logs and a sample of the JSON stored in your _airbyte_data columns for this stream?
I guess the screenshot you shared is from a final normalized table in snowflake and I’m wondering if the problem comes from the normalization or the connector itself.

3

Hi @alafanechere ,

Here’s the sync logs
logs-10162.txt (35.4 KB)

here’s a sample of the JSON stored in the _airbyte_data column for this stream, looks like the Squad field is not even being picked up

  "acaStatus": "",
  "acaStatusCategory": null,
  "bestEmail": "",
  "city": "Montreal",
  "country": "Canada",
  "createdByUserId": "2485",
  "department": "Engineering",
  "displayName": "",
  "division": "",
  "employeeNumber": "106",
  "employmentHistoryStatus": "Full-Time",
  "ethnicity": null,
  "firstName": "",
  "flsaCode": "1",
  "fullName1": "",
  "fullName2": "",
  "fullName3": "",
  "fullName4": "",
  "fullName5": "",
  "hireDate": "2020-05-25",
  "homeEmail": "",
  "homePhone": "",
  "id": "122",
  "jobTitle": "",
  "lastChanged": "2022-06-16T13:53:47+00:00",
  "lastName": "",
  "location": "",
  "middleName": "",
  "mobilePhone": "",
  "originalHireDate": "0000-00-00",
  "preferredName": "",
  "stateCode": "",
  "status": "Active",
  "supervisor": "",
  "supervisorEId": "",
  "supervisorEmail": "",
  "supervisorId": "",
  "terminationDate": "0000-00-00",
  "workEmail": "",
  "workPhone": "",
  "workPhoneExtension": "",
  "workPhonePlusExtension": "",
  "zipcode": ""
}
4

Hi @kyle-cheung,
Thanks for the details, I think the error is on the Bamboo HR connector side.
It would help to troubleshoot (and eventually open a Github issue) if you could share your catalog.json file. You’ll find instructions on how to get this file here.

5

Hi @alafanechere , sorry for the late response. I was out a few weeks. Here’s the catalog.json file, also I think the instructions need to be updated because now the files look to be split into source_catalog.json and destionation_catalog.json.

I’ve saved the file as .txt since discourse does not let me upload a .json file
catalog.txt (18.3 KB)

6

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.