Table sync keeps a datastore in ActiveManage aligned with an external table of record — typically a master data system or a partner's database. It runs scheduled or on-demand jobs that pull (and/or push) changes, applying conflict resolution rules and preserving an audit trail.
Direction Modes
- Pull-only: ActiveManage receives changes from an external source; doesn't push back. Best for master-data systems.
- Push-only: ActiveManage acts as master; pushes changes outward. Best for distributing canonical data.
- Bidirectional: Changes flow both ways. Requires careful conflict resolution.
What Gets Synced
- Inserts — new rows on either side.
- Updates — modifications to existing rows.
- Deletes — soft (mark as deleted) or hard (remove the row).
- Optionally: relationships, attachments, custom fields.
Identifying Rows
Each row needs a stable key that's consistent across both systems. Typical patterns:
- Source system's primary ID stored in a sync_external_id column.
- A natural key (email address, SKU code).
- A purpose-built UUID generated once and copied to both sides.
Worked Examples
- Customer master sync: Salesforce → ActiveManage, pull-only, hourly. Every Salesforce Contact becomes an ActiveManage user.
- Product catalogue distribution: ActiveManage → 3 partner sites, push-only, real-time on every save. Each partner site mirrors the catalogue.
- Order bidirectional: Orders flow between ActiveManage and warehouse-management system. Status updates go in both directions; conflicts resolved by timestamp.