Connector Improvement: Lever
AnsweredLever allows you to have confidential requisitions postings and opportunities (any opportunity attached to a confidential posting) these postings and opportunities currently are not being posted to snowflake. My best guess is this is because they have to be specifically requested using a parameter confidentiality=all when making the request. Confidential data is documented here https://hire.lever.co/
One more key piece of information if you request a specific record that is confidential it will return the record but if you request multiple records or the full list of records it will only send back the non-confidential records.
Without this functionality it causes reporting issues since we do not have confidential reqs in Snowflake and this is a requirement for us. With out this we can not rely on the data that is being brought in since it is incomplete.
Ideally the confidential data would be posted to the correct tables as well as identified as confidential in another column the api returns a node "confidentiality" that could be used to tell if it is confidential or not
-
Official comment
Hi Keith -
Thanks for submitting this feature request. We have added the functionality to sync confidential opportunities, however I have added a secondary item to also sync the confidential requisitions. I will add this to our backlog and prioritize for a future sprint.
Thanks,Erin
-
We also have this issue. Could anyone support here?
-
Erin we now see the confidential reqs but it does not look like you added the confidentiality field. can you confirm that you added this field to the mapping and/or why we do not see it on our database tables. I think it should be on the opportunity, postings, and requisition tables
-
It would be required to have the Confidentiality field added to these tables to help differentiate
Please sign in to leave a comment.
Comments
4 comments