Hi Young-Eun,

Thanks for submitting this feature request. Due to limitations at the source, currently the only way to capture deletes in these tables is to request a full resync through our Customer Service team. Unfortunately, this can be very time-consuming. We are actively looking into ways to improve this.

It would be great to understand your use case a little more. Can you describe the scenarios where responses are deleted or retaken? How frequently does this happen?

Best,

Sadie

Hi Sadie! Thanks for checking. I agree that it's not a sustainable solution to have the Customer Service team resync each time.

Right now, we ask people to take surveys to periodically give us the state of some of their attributes. However, some of those questions can lead to them retaking it since they misunderstand what we are asking for. Not ideal on our side either and we're also looking into ways of capturing that data besides surveying. We are deduping downstream according to the attributes, but this leads to ambiguity on which subsequent survey responses were corrections from retaking versus a true subsequent periodic response.

Hey Sadie,

we have a similar issue with Qualtrics not covering deleted rows (e.g. in the survey response table). We would except a column `_fivetran_deleted` to track deleted rows. 
In your last response, you mentioned that you consider enabling this feature. What is the current status on it?

Best,

Niklas

I'm seeing this has still not been addressed, so adding my two cents. A weekly update to capture those rare deletes would be sufficient for our purposes.

Hi All,

Thanks for the upvotes and comments! We agree this is a valuable problem to solve and have picked this up as a near-term initiative. We will keep the community informed once this is planned and rolled out.

Thanks,
Vignesh

What is the timeline for this update? We are pulling deleted Qualtrics surveys into our data warehouse with no way to distinguish them from valid survey responses. Pretty critical feature.