You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected: We expect the tap to capture estimate messages for every estimate.
Actual: When creating multiple estimate messages prior to a sync job the tap only sends a record for the last created estimate message. So, if multiple estimates are acted on e.g. sent, declined, approved, the tap will only capture the action that occurred last.
To reproduce: Create a message in Estimate A by marking it as accepted. Then create two messages in Estimate B by marking it as accepted and then sent. The expectation is unclear whether only the last message should be sent for each estimate or if all messages should be sent for each estimate. Regardless, the tap should capture more than just the last created message.
This defect is true for the following streams:
invoice_messages
invoice_payments
The text was updated successfully, but these errors were encountered:
kspeer825
changed the title
tap does not handle estimate_messages correctly
tap does not handle estimate_messages/invoice_messages correctly
Dec 4, 2019
kspeer825
changed the title
tap does not handle estimate_messages/invoice_messages correctly
tap does not handle invoice/estimate_messages and invoice payments correctly
Dec 4, 2019
Expected: We expect the tap to capture estimate messages for every estimate.
Actual: When creating multiple estimate messages prior to a sync job the tap only sends a record for the last created estimate message. So, if multiple estimates are acted on e.g. sent, declined, approved, the tap will only capture the action that occurred last.
To reproduce: Create a message in Estimate A by marking it as accepted. Then create two messages in Estimate B by marking it as accepted and then sent. The expectation is unclear whether only the last message should be sent for each estimate or if all messages should be sent for each estimate. Regardless, the tap should capture more than just the last created message.
This defect is true for the following streams:
invoice_messages
invoice_payments
The text was updated successfully, but these errors were encountered: