Hi all! For the ones working with the google ads / bingads source connectors and incremental + history deduped sync. I just realized that as the cursor is set by default to segments.date in google ads (for example for campaigns table), or to timeperiod in bing ads (for example in ad_group_performance_report_daily), it will never update records, only add new ones!! Which is a disaster for me. Is it correct what I´m saying? if so, how do you work with it??

Hello laila ribke, it's been a while without an update from us. Are you still having problems or did you find a solution?

Hi, still have this issue as those source connectors have cursor that can't been set up. The cursor is id, therefore whenever there is an update in any field in the row, it won't be updates, as the id didnt change. It works just for adding new fields (new id's) that havent been before, but not for updating existing fields

Were you able to resolve the issue with the ids here?

Hi, no, same issue still without solving

Hi! I have the same issue here. And there is another problem: for example for Google Ads and the table campaigns, the primary key field should also include segments.hour. The consequence of this is that, for a given campaign and date, the final table contains only one row out of the 24 possible. I can still work with the

_scd

table to work around the problem but it is a bit of a hack

Hey Baudoin, Sorry to hear you're experiencing the same issue. Could you upgrade the connectors to the latest and try again? (There was an update that I'm seeing in the changelog that might have solved this issue. Thanks for being patient!