This release updates the Absorb Salesforce App so that saving a change to a Field Mapping automatically reprocesses all previously synced Users, Contacts, and Person Accounts tied to that mapping. The reprocessing runs during the next scheduled Sync Batch, eliminating the need for custom Apex scripts or manual record updates to backfill historical records after a mapping change.

This section describes the new retroactive sync behavior in the Absorb Salesforce App.

For more information on the Absorb Salesforce App, including how data flows between Salesforce and Absorb, see:

• Absorb Salesforce App Overview

Retroactive Sync After a Field Mapping Change

Previously, the Absorb Salesforce App used delta sync, meaning only records that changed in Salesforce since the last sync were processed. When a new Field Mapping was added or an existing mapping was modified, previously synced records retained their original values until they were independently updated at the source. Backfilling existing records required a custom Apex script or manual record updates.

With this release, saving a change to a User, Contact, or Person Account mapping automatically flags all previously synced records of the affected type for reprocessing. The updated mapping is then applied during the next scheduled Sync Batch.

The behavior applies whenever a mapping change is saved:

• Adding a new mapping, modifying an existing mapping, or removing a mapping all trigger reprocessing on the next batch.
• Reprocessing runs during the next scheduled Sync Batch, which executes approximately every 30 minutes.
• Records where the updated mapping does not produce a different value are skipped, preventing unnecessary writes.
• The sync completes silently, no confirmation message is shown.

This release applies to User, Contact, and Person Account field mappings only. Course and Enrollment mapping changes are out of scope. For full configuration details, refer to the Absorb Salesforce App Overview.