Open richarddenys opened 5 years ago
This issue sounds very similar to https://github.com/singer-io/tap-pipedrive/issues/31. I think we'd just need to adjust the JSON schema to allow a null value here.
A PR to edit this line of code https://github.com/singer-io/tap-pipedrive/blob/master/tap_pipedrive/schemas/recents/files.json#L8
It's possible in Pipedrive to have a file with no user associated. This happens when a Pipedrive user that added a file to a deal is deactivated/removed. In the Pipedrive UI, this appears as "(hidden user)":
Via the API, this appears as
'user_id': None
which doesn't match the integer type expected. See the result here with Stitch:I'm not familiar with how to be able to fix this. Can anybody help please?