Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BambooHR Custom Fields Delivered As NULL #15170

Closed
marcosmarxm opened this issue Aug 1, 2022 · 5 comments · Fixed by #16826
Closed

BambooHR Custom Fields Delivered As NULL #15170

marcosmarxm opened this issue Aug 1, 2022 · 5 comments · Fixed by #16826

Comments

@marcosmarxm
Copy link
Member

This Github issue is synchronized with Zendesk:

Ticket ID: #1613
Priority: normal
Group: Community Assistance Engineer
Assignee: Marcos Marx

Original ticket description:

This is a repost of (https://discuss.airbyte.io/t/bamboohr-custom-fields-not-pulling/1580)

  • 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

Below is what the results come through as at the destination schema. All NULL
image

This is what it looks like on the front end in BambooHR
image

Here are the logs
logs-10162.txt (35.4 KB)

And a sample of the JSON stored in _airbyte_data column

 "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": "",

And here is the catalog.json file as requested previously
catalog.txt (18.3 KB)

[Discourse post]

@marcosmarxm
Copy link
Member Author

Comment made from Zendesk by Marcos Marx on 2022-07-15 at 18:21:

Kyle can you share the output from the BambooHR showing how the custom field is returned? You can only post the custom field and remove the rest

@marcosmarxm
Copy link
Member Author

Comment made from Zendesk by Marcos Marx on 2022-07-19 at 15:59:

Hi @marcosmarxm this is how BambooHR shows it on the front end

And this is how it is returned when delivered to Snowflake

[Discourse post]

@marcosmarxm
Copy link
Member Author

Comment made from Zendesk by Marcos Marx on 2022-07-28 at 16:12:

@marcosmarxm any updates on this?

[Discourse post]

@marcosmarxm
Copy link
Member Author

Comment made from Zendesk by Marcos Marx on 2022-08-01 at 19:31:

Unfortunately no, Airbyte integration test account is not working. I escalated the issue to Github #15170 any updated I'll return to you.

@midavadim
Copy link
Contributor

@lazebnyi @marcosmarxm

I was not able to find any tutorials on how to add new custom field in BambooHR.
I tried to create new employees with custom 'bla' field via API, but I was not able to extract it back neither via reports API nor get_employee API.

So, we probably need to ask our client for more information:

  1. if possible, please provide us with steps how you added new custom field to BambooHR.
  2. provide us with a full link to BambooHR UI page where you can see your custom field and screenshot of the whole page.

Overall, my vision is that custom reports support fields specified on this page only (as it is mentioned in our spec):
https://documentation.bamboohr.com/docs/list-of-field-names

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants