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

Tap does not write all fields for certain streams to target #37

Open
kspeer825 opened this issue Dec 19, 2019 · 1 comment
Open

Tap does not write all fields for certain streams to target #37

kspeer825 opened this issue Dec 19, 2019 · 1 comment

Comments

@kspeer825
Copy link
Contributor

kspeer825 commented Dec 19, 2019

Expected: Tap-Harvest should send all fields for a given stream to the target, based on the V2 Harvest API. We are defining the expectations for which fields should be sent based on what is returned in the response of a get call to the Harvest API.

Actual: Tap-Harvest sends all fields for most streams with the following exceptions.
Stream: fields
roles: user_ids
clients: statement_key
invoices: recurring_invoice_id, period_start, paid_at, paid_date, closed_at, period_end
estimates: declined_at, accepted_at
time_entries: timer_started_at, rounded_hours

From this group the following fields were confirmed by warnings in the tap-tester logs.
Stream: fields
roles: user_ids
clients: statement_key
invoices: recurring_invoice_id

@kspeer825
Copy link
Contributor Author

kspeer825 commented Jan 3, 2020

The following appear to be a test issue, not a bug. These streams are not captured as a result of not creating the necessary data to:
Stream: fields
invoices: recurring_invoice_id, paid_at, paid_date, closed_at
estimates: declined_at, accepted_at

@kspeer825 kspeer825 reopened this Feb 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant