0
Not a bug

After the key of an object is changed polling creates a new object but doesn't delete the old one

Adrian Corston 2 weeks ago in UNIFYBroker/Microsoft Active Directory • updated by Adam van Vliet (Chief Information Security Officer) 2 weeks ago 1

When using polling with the AD connector, a new record is created for objects where any attribute that is part of the key has been changed, and the old object is not removed.  This either means that the polling functionality is not useful, or else the connector cannot be usefully used with any key other than objectGUID.

If this behaviour can't be improved then it really should be mentioned in the documentation for the connector since it's quite important.

Affected Versions:
Fixed by Version:

Answer

Answer
Not a bug
Depending on the specification of the target system we are not always able to retrieve deletions during polling import. This is one of the reasons full imports are scheduled and not just relying on polling. This is unfortunately the case with this connector, as it uses the uSNChanged method, which doesn't surface deletions. I will take a note to update the documentation. Thanks.
GOOD, I'M SATISFIED

I think you should mark this as "Can't Fix" rather than "Not a bug".

Satisfaction mark by Adrian Corston 2 weeks ago
Answer
Not a bug
Depending on the specification of the target system we are not always able to retrieve deletions during polling import. This is one of the reasons full imports are scheduled and not just relying on polling. This is unfortunately the case with this connector, as it uses the uSNChanged method, which doesn't surface deletions. I will take a note to update the documentation. Thanks.