Two-way sync
Changes in Dynamo DB or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Keep Dynamo DB and Servicemax in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Engineers integrate with tools like Servicemax through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in Dynamo DB.
Stacksync mirrors Work Orders, Work Details, Installed Products, Service Contracts from Servicemax into DynamoDB Streams, Global Tables, Tables, Items in Dynamo DB and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Servicemax, so the tool and the database never disagree.
Updates in Servicemax arrive as row changes in Dynamo DB, so triggers, jobs, and services can respond in near real time.
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
Records from Servicemax are ordinary rows in Dynamo DB; join them, index them, and use them in application logic without touching the vendor API.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Dynamo DB objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Partition and Sort Keys The primary key pair used as the match key for bi-directional sync. | Work Orders SVMXC__Service_Order__c; the core field-service job record for install, repair, and maintenance; synced two-way with databases and pushed to ERPs at close. | Partition and Sort Keys is specific to Dynamo DB and Work Orders to Servicemax — each maps to any object or custom field on the other side. | |
| Global Secondary Indexes Alternate access paths used when sync queries filter on non-key attributes. | Work Details SVMXC__Service_Order_Line__c; line items on a Work Order for labor, parts used, and expenses; read out for billing or written back with usage. | Global Secondary Indexes is specific to Dynamo DB and Work Details to Servicemax — each maps to any object or custom field on the other side. | |
| DynamoDB Streams Ordered item-level change records consumed for incremental sync. | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | DynamoDB Streams is specific to Dynamo DB and Installed Products to Servicemax — each maps to any object or custom field on the other side. | |
| Global Tables Multi-region replicas relevant when syncs must read from a specific region. | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Global Tables is specific to Dynamo DB and Service Contracts to Servicemax — each maps to any object or custom field on the other side. | |
| Tables The top-level containers a sync targets; each table is addressed independently. | Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Tables is specific to Dynamo DB and Stock History to Servicemax — each maps to any object or custom field on the other side. | |
| Items Schemaless records keyed by partition (and optional sort) key, mapped to rows or SaaS objects in syncs. | Accounts Standard Salesforce Account; customer and site company records; synced two-way with CRM and database customer tables. | Items is specific to Dynamo DB and Accounts to Servicemax — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionChanges in Dynamo DB are captured at the source via change data capture — no polling loop against its API. Item-level change streams via DynamoDB Streams or Kinesis Data Streams integration.
DeliveryEach detected change is written to Servicemax through its API, with automatic retries and rate-limit backoff.
DetectionChanges in Servicemax are captured at the source via change data capture — no polling loop against its API. Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object.
DeliveryEach detected change is applied to Dynamo DB as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Dynamo DB–Servicemax connection.
Changes in Dynamo DB or Servicemax instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Dynamo DB or Servicemax data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Dynamo DB or Servicemax record.
Track your Dynamo DB ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Dynamo DB and Servicemax.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate Dynamo DB and Servicemax with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Dynamo DB and Servicemax objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Dynamo DB and Servicemax: authenticate both systems, choose the objects to sync (such as Dynamo DB's Partition and Sort Keys and Global Secondary Indexes), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Servicemax side: Work Orders, Work Details, Installed Products, Service Contracts, plus custom fields where Servicemax exposes them. On the Dynamo DB side: DynamoDB Streams, Global Tables, Tables, Items. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Dynamo DB and Servicemax: React to changes as they happen; One integration pattern for the whole stack; Read Servicemax with a query. Updates in Servicemax arrive as row changes in Dynamo DB, so triggers, jobs, and services can respond in near real time.
Dynamo DB: Proprietary JSON-over-HTTPS API accessed through AWS SDKs; PartiQL supported for SQL-like queries. Authentication: AWS IAM credentials with SigV4 request signing. Servicemax: Salesforce REST, SOAP, and Bulk APIs (ServiceMax is a managed package on the Salesforce platform). Authentication: Salesforce OAuth login via a user with API access; the connecting profile needs object and field permissions on ServiceMax's SVMXC__ objects. Stacksync manages authentication, retries, and rate limits on both sides.
Servicemax: ServiceMax Core runs as a managed package on Salesforce (SVMXC__ objects); Asset 360 is native on Salesforce Field Service, so all access goes through the Salesforce API. Dynamo DB: Queries are efficient only along key and index access paths; full-table scans are expensive, which makes stream-based sync preferable to polling. Stacksync's field mapping accounts for these differences between Dynamo DB and Servicemax without custom code.
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 455 integrations available for Dynamo DB and Servicemax.