Qeasy Cloud
Get Started

Customer Master Data Sync from ERP to Collaboration Platform: A Practical Walkthrough of One Strategy

· 高金凤· Integration Solutions· 14 views· 4 min read

What This Strategy Solves

Customer master data is the foundation of any supply chain integration. In one real project, a retail enterprise kept customer records in an ERP system while running visits, contracts, and reconciliation in a collaboration platform. After three months of dual entry, codes, names, and owning organizations no longer matched, and the business units started pointing fingers. The safest remedy is treating the ERP as the single source of truth and the collaboration platform as a pure consumer. This article dissects exactly that kind of strategy: incrementally pushing customer records from the ERP into the collaboration platform's form instances by code.

Data Flow and Field Mapping

The overall flow is ERP → Qeasy Data Integration Platform → Collaboration Platform Form. The middleware layer only handles retrieval, mapping, and push — it does not persist business data.

Business MeaningERP Field (Source)Collaboration Platform Form Field (Target)Notes
Customer CodeFNumbertextField_… (Customer Code)Primary key, basis for incremental sync
Customer NameFNametextField_… (Customer Name)Direct pass-through
TypeFixed valuetextField_… (Type)Hardcoded as "Customer"
Type CodeFixed valuetextField_… (Type Code)Hardcoded business dictionary code
Create OrgFCreateOrgId.FNumberMapped on form sideMust be unified in middleware for multi-org
Use OrgFUseOrgId.FNumberMapped on form sideSame as above

The code field also serves as the idempotency key, ensuring the same customer pushed repeatedly does not create duplicates.

How to Configure on Qeasy

We use the Qeasy Data Integration Platform to host this strategy. The key is not "making it work" but making it maintainable later.

  1. Source-side retrieval: In the source system adapter, select the ERP's customer document query interface. Only pick the fields needed for this run — keep the payload lean. For multi-org customers, always include "Create Org" and "Use Org"; otherwise the downstream cannot locate ownership.
  2. Centralized code mapping: Put the mapping from ERP codes to the collaboration platform's business dictionary into Qeasy's mapping table rather than hardcoding it in scripts. When new organizations or customer types are added later, you only update one table instead of touching the sync body.
  3. Target-side configuration: Use the form-instance creation interface on the target side. Put base fields (name, code, type, type code) into the request body, and place app identifiers, user identifiers, etc., into otherRequest. After submission, write the returned instance ID back into Qeasy's association table as the basis for subsequent updates or lookups.
  4. Idempotency and switch: Enable "idempotency by code" — repeated triggers on the same code only update, never create. Add a "dry-run" switch so that newly onboarded organizations can run for two weeks of verification before going live.

Implementation Steps

  • Phase 1: Full initialization. Pull all active customers from the ERP and push them over in one shot. This is usually triggered manually. After completion, do a sample comparison to verify names, organizations, and types before moving into daily sync.
  • Phase 2: Switch to incremental start point. Take the moment when the full sync finishes as the starting point. The source side pulls increments based on "last modified time > last sync watermark". The incremental strategy must run in the same pipeline as the full sync — do not split them into two configurations, or the watermark will desynchronize.
  • Phase 3: Daily scheduling. The source side triggers at 5 minutes past every hour (that 5 * * * * string in the config means exactly that), and the target write happens every 20 minutes (*/20 * * * *), forming a rhythm of "fast source, stable target". Higher frequency is not better — for basic data like customer records, an hourly cadence is fully sufficient.
  • Phase 4: Exception handling. Configure retry and alerting on the Qeasy side. Common failures include codes already occupied on the collaboration platform or required fields being empty. These cases appear in the logs with specific document references, so you fix them and manually re-push.

Pitfalls and Lessons Learned

  1. Using "code + name" as a composite primary key. The collaboration platform usually uses an instance ID as the primary key, but cross-system sync must use a business code as the idempotency key. A typical mistake is using the name for deduplication — when two customers share a name, one gets silently skipped.
  2. Missing multi-org fields. ERP customer records often carry "Create Org" and "Use Org". Leave one out, and downstream sales reps cannot tell who owns the record, so everything gets bounced back.
  3. Using two configurations for full and incremental sync. The safe approach is to use a "watermark field" inside a single pipeline: run full sync first, then incremental, with the watermark advanced automatically by Qeasy.
  4. Hardcoding dictionaries in scripts. Enumerations like customer type and organization look stable, but they change every six months. A common pattern among Qeasy customers is to extract these into a mapping table — change one place, and it takes effect everywhere.
  5. Ignoring soft deletes. Customers deactivated in the ERP get pushed through and produce "zombie records" in the collaboration platform. The safe approach is to add an "is active" filter in the middleware and only push active customers.

Suitable and Unsuitable Scenarios

Suitable: The ERP is the single source of customer master data, and downstream systems like collaboration platforms, OA, or CRM need to consume it, with the downstream allowing idempotency by code. Unsuitable: Bi-directional editing (both sides modify customer records), multi-source customer maintenance, or scenarios requiring complex approval workflows — those are better served by an MDM platform rather than one-way sync.

Original content. Please credit the source when reposting: https://www.qeasy.cloud/insights/solutions/strat-kingdee-cloud-dingtalk-9365-basic-ky-v4-0-7c70682e

Comments