I’m having some trouble with the parent-child rela...
# troubleshooting
m
I’m having some trouble with the parent-child relationship in `tap-pardot`: • The
list_membership
stream filters by
list_id
(parent) AND
listmemberhip.id > bookmark
. • I’m not 100% I’m reading the implementation correctly, but I believe that even when the
list_memberships
stream is called independently, it pulls all of the
lists
id’s (sorted by
updated_at
and loops through them to do the sync, so it should only sync lists that have been updated. • So if (assuming the letters are chronological order) the parent lists are processed in the order
list_b (list_member ids 100, 101, 102)
,
list_a (list_member ids 1, 2, 3)
then none of the list_members from
list_a
will be synced because their ids are all
< 102
I figure I can just remove this line, but I’m concerned potentially concerned that it will mess with the incremental replication (and potentially won’t actually solve the issue. I’m also a little confused why they didn’t just us use the
UpdatedAtReplicationStream
for
list_membership
? Any advice?
For what it’s worth I confirmed this behavior. Not sure if my org is just using some sort of anti-pattern here, but it seems like a pretty solid bug. I think the real answer is to build a new tap that uses the SDK and v5 of the api…