Connector Improvement: ServiceNow connector - reflect reclassification of CMDB records
Completed
Please update _fivetran_deleted to TRUE when on source table when CI is reclassified.
When a record is re-classified in ServiceNow within the Configuration Management Database (CMDB) it is moved from one table to another - however Fivetran does not track this change and so maintains two records when there should be just one.
This is a relatively common scenario in ServiceNow which you can read about here.
Here's their notes on what happens with reclassification and my own notes on implication for data replicated via Fivetran:
When you reclassify a CI, the following occurs.
-
The set of attributes is adjusted to match the set of attributes of the newly assigned class. Attributes are added or removed as needed.
-
If any attributes are unique to the current class and are not defined in the newly reclassified class, they are lost.
-
A new record with the CI's current sys_id is inserted to the table of the new class, with the appropriate set of attributes for the class (the sys_id of the CI is retained).
When the 'new' record is created, the 'old' record is not removed nor flagged as deleted.
The expected result would be flagging as _fivetran_deleted (which would need to be derived rather than gathered from ServiceNow's own audit of deleted records). As step three mentions - a 'new' record with same sys_id is created which means the original is deleted from the source table (see KB0727701 as reference).
-
Official comment
Hi Andrew,
Closing this request as this has been discussed separately.
Thanks,
Frank -
Andrew,
Thanks for raising this request. I will have the team look into this when we have capacity and add it to the backlog.
Thanks,
Frank
Please sign in to leave a comment.
Comments
2 comments