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
[TDL-24255] Fix for attribute & generated relationship name #32
Conversation
…eam for followUpSequenceId attribute.
Did an alpha for the customer and their connection is working now with changes in this PR. |
tap_outreach/sync.py
Outdated
@@ -251,7 +251,7 @@ def process_records(stream, mdata, max_modified, records, filter_field, fks): | |||
'null or `id` field expected for `data` relationship') | |||
|
|||
# potential fix for the issue - https://github.com/singer-io/tap-outreach/issues/20 | |||
if stream.tap_stream_id not in ["prospects", "events"]: | |||
if stream.tap_stream_id not in ["prospects", "events", "mailings"]: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If a stream encountering this exception means we have to come in and say "and don't throw for this stream" then why are we throwing this exception at all?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…generated relationship name.
Description of change
JIRA
Fixed attribute & generated relationship name issue with mailings stream for followUpSequenceId attribute.
Manual QA steps
Risks
Rollback steps