Connector Improvement: When records from extended table are deleted in ServiceNow, their corresponding records in base table(s) are not marked as deleted in the destination if extended table is not being synced
CompletedI would like to kindly request a feature improvement that would enable the capture of deletions for records in base tables across all levels, regardless of the extended table's sync status. This enhancement is essential for ensuring that the data in Snowflake accurately reflects the state of data in ServiceNow. Without this capability, it becomes challenging to trust the data, which can impact the reliability of reports and decision-making processes.
Please refer below example for more details:
Let's assume Fivetran sync is enabled for cmdb_ci & cmdb_ci_firewall_network tables and sync is not enabled for cmdb_ci_computer table.
When a record is deleted in cmdb_ci_firewall_network table in ServiceNow, Fivetran correctly mark _fivetran_deleted = True for the records having same sys_id in cmdb_ci_firewall_network & cmdb_ci tables in the destination. However, when a record is deleted in cmdb_ci_computer table in ServiceNow, Fivetran does not mark _fivetran_deleted = True for the record having same sys_id in cmdb_ci table in the destination.
Thank you for considering this request.
-
Official comment
Hi,
As discussed via email, we have a potential feature that will help address this issue. Closing this request for now as we rollout this new feature.
Frank
Please sign in to leave a comment.
Comments
1 comment