Skip to content

Cross-System ID Mapping

Publish an ID map entity that ETL and AI can query—instead of hiding crosswalks only inside a golden record.

Why this is needed

  • Integrations fail on ambiguous joins.
  • Golden-record MDM is not always the first step.
  • Agents need stable identifiers when retrieving context.

Proposed entities in EntiHub

Governance settings

Setting Recommended value Why
approvalRequired true Wrong mappings break payments and CRM.
historyEnabled true History of remaps for incidents.
allowSameAuthorApproval false Maker/checker separation for sensitive changes.
deletedRetentionDays 90 (or higher) Soft-delete retention for auditability.

Entity definition (YAML sketch)

name: id_map
displayName: ID map
domain: Integration
description: ID map
version: "1.0.0"
approvalRequired: true
historyEnabled: true
deletedRetentionDays: 90
displayRefColumn: map_code
uniqueConstraints:
  - name: uq_id_map_0
    columns: [entity_type, source_system, source_id]
columns:
  - name: map_code
    dataType: string
    nullable: false
    maxLength: 64
  - name: entity_type
    dataType: string
    nullable: false
    maxLength: 32
  - name: canonical_id
    dataType: string
    nullable: false
    maxLength: 64
  - name: source_system
    dataType: string
    nullable: false
    maxLength: 32
  - name: source_id
    dataType: string
    nullable: false
    maxLength: 128
  - name: status
    dataType: string
    nullable: false
    maxLength: 16

YAML sketches

Sketches highlight the important fields and governance flags. Trim or extend columns to match your domain. See Setup Entity for the full YAML reference.

Sample data

map_code entity_type canonical_id source_system source_id status
MAP-C-100 customer CUST-190 SAP 0000100190 active
MAP-C-101 customer CUST-190 CRM 0011Q00002ABC active

Benefits for the company

  • ETL and AI share one correlation store.
  • Unique constraints prevent duplicate source keys.
  • Complements classic MDM.