AnonymizeBatch now also cleans up Address Change records

Introduction

When anonymising candidates via the AnonymizePersonsBatch, the candidate's default address was cleared, but linked Address Change records (msf__Person_Address__c) were retained when the Use Address Changes setting in the Software Changes custom setting was enabled. This resulted in incomplete anonymisation and a potential privacy risk.

With this improvement, Address Change records are now also correctly processed during anonymisation, in line with the existing GDPR clean-up logic.

Who is this feature relevant for?

• Application administrators who use the AnonymizePersonsBatch and have the Use Address Changes setting enabled.
• Organisations that want to fully anonymise candidate data in accordance with GDPR requirements.
• Organisations with an active synchronisation from MSR to MSF (Business Central).

Feature explanation

Processing of Address Change records

• Processing is only active when the Software Changes → Use Address Changes custom setting is enabled.
• Records with Effective Date = empty: the record is anonymised and retained. Only the fields Id, Person, BC System ID and Address Type remain populated; all other fields are cleared.
• Records with Effective Date filled in: the record is deleted.

Synchronisation to Business Central (MSF)

• After the batch has completed, anonymised Address Change records are passed to Business Central via an update synchronisation.
• Deleted Address Change records are passed to Business Central via a delete synchronisation.
• Synchronisation only takes place when the candidate has a BC Resource number (i.e. is known in MSF). For non-synchronised candidates, addresses are only cleaned up in MSR.

Other features in this release

🔗 Find all features from this release here