Skip to content

How-to guide

Model a domain from two sources

Model a domain from two sources

2 min

Goal: locate a customer's orders without confusing CRM and ERP identifiers. Estimated duration: 30 minutes excluding synchronization. Access: configure sources and edit the model.

Prepare sample records

Use a test workspace with Ontologie and Live Data available. Choose a known customer in each source and a corresponding order. Record references and observation dates before linking sources.

SourceSample recordIdentifier to retain
CRMACME Francecrm_id = CRM-42
ERPACME Franceerp_id = ERP-901
ERPOrder CMD-001client_erp_id = ERP-901

These are sample values. Identical names do not prove a match. Use a reviewed correspondence table or a reliable shared key. If absent, retain both identifiers separately and report the unresolved match.

1. Define the minimal model

Create Client and Commande using the quickstart. Define source reference properties and document which source supplies each value. Add currency for amounts and specify time zones for dates.

Define the direction of Client places Commande. client_erp_id must correspond to the selected ERP customer; a field in a row does not establish a navigable relationship by itself.

Configure sources using connectors. Select the necessary streams and verify successful synchronization. Inspect links and available field mappings in the type's Sources tab.

Do not overwrite a CRM value with an ERP value without choosing the system of record. For example, document “name supplied by CRM; order reference supplied by ERP”.

3. Verify accessible records

Locate the three samples in Instances or the linked spreadsheet. Compare references, values and origins with source records. Check the last successful synchronization and active filters.

Also test a namesake and an order without a corresponding customer. Expect an explicit match for CMD-001 and reported ambiguity for unresolved cases, without assuming automatic merging.

Limits and next step

Source linking is not an identity-resolution policy. Correct external records in their source, then synchronize. See Diagnose missing data for missing values. Once verified, prepare a question using records and documents.

Did this page help you achieve your goal?