A Data replication app using Microsoft Dynamics 365 / CE / CRM as the source will create the Scribechangehistory custom entity within the CRM organization, which is used to track when records are deleted in CRM. This entity is referenced when the Data replication app runs to update the "Scribe_DeletedOn column" for the deleted record within the target datastore. By default, records in the Scribechangehistory table are purged 60 days after the last modified date.

There may be instances where the Scribechangehistory table is too large and records more recent than the 60 day last modified date would need to be purged.

How to properly delete records from the the Scribechangehistory custom entity in Microsoft Dynamics 365 / CE / CRM.

To purge additional records from the Scribechangehistory table, it must first be determined if the deleted records being purged have already been synced via the Data replication app to the target datastore. To do this, find the most recent modified date of the set of records to be purged from the Scribechangehistory table. Look up this record within the target datastore to see if the "Scribe_DeletedOn column" has been updated to show that this record was deleted in CRM. If the "Scribe_DeletedOn column" is correctly updated, then the chosen set of records being purged from the Scribechangehistory table have been synced and can be purged without issue.