Summary
Inquiry about the change in refresh behavior of Pardot source streams from incremental to full refresh after the transition to low-code/manifest-only in the latest release.
Question
I know this is a long shot, but does any one happen to know why the Pardot source streams were all made full refresh only when it was moved to low-code/manifest-only in the latest release? (Previously they were able to be incremental, seems like an odd limitation.)
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
['pardot', 'source-streams', 'full-refresh', 'incremental', 'low-code', 'manifest-only']
<@U06PQ377AU9> <@U069EMNRPA4> maybe have more context.
Dammit. Regressions happen! And I think I want a CI check on this one.
I think that it should be straightforward to add incremental cursors back in the builder. Want to try that? If it’s feasible, I’ll help with merging quickly
<@U069EMNRPA4> I should be able to tackle it, but am working a time-sensitive deadline . . . so might be a couple weeks before I can free the capacity to jump in
<@U06PQ377AU9> <@U069EMNRPA4> maybe have more context.
Dammit. Regressions happen! And I think I want a CI check on this one.
I think that it should be straightforward to add incremental cursors back in the builder. Want to try that? If it’s feasible, I’ll help with merging quickly
<@U069EMNRPA4> I should be able to tackle it, but am working a time-sensitive deadline . . . so might be a couple weeks before I can free the capacity to jump in