Field-level sync aligns IT Hardware Asset Management and Configuration Management Database records. Event-driven sync resolves data conflicts, translates values, and stops infinite update loops. This framework makes sure that the IT team finds accurate inventory details.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, and Unlimited Editions with Agentforce IT Service. |
Field-Level Sync
Mapped fields keep critical data points consistent between hardware assets and linked CIs. This automated framework syncs standard and custom field values across systems.
To manage dataflow, configure these layers:
- Field Mapping: Link specific asset fields to CI fields with the Configuration Management Item Field Map. Configure up to 40 field mappings per sync rule.
- Field Value Mapping: Translate picklist options and specific values between systems with the Configuration Management Item Value Map.
Field Types and Conversion Rules
CI field sync supports data mapping and formatting rules that govern how field values convert between systems.
- Boolean to Boolean: Maps boolean values directly between systems while preserving the exact logical truth value.
- Date to Date: Converts date values between systems while preserving the exact calendar date.
- DateTime to DateTime: Converts outbound values to UTC ISO-8601 strings while preserving the exact instant.
- Date to DateTime: Converts Date values to midnight UTC (00:00:00.000Z).
- DateTime to Date: Normalizes the instant to UTC and derives the corresponding UTC calendar date.
- Record ID to Text: Converts a Salesforce Record ID into its alphanumeric string representation for storage in plain-text fields.
- Text to Text: Maps string values directly between systems while preserving the exact character sequence and text content.
We don’t allow datetime to text, text to datetime, text to boolean, and boolean to text, text to record ID conversion rules.
Source of Truth and Ownership
Designate a single source of truth for each mapped field to preserve data integrity. The source of truth determines the authoritative system and dictates update directions.
Authoritative assignments typically follow these categories:
- Asset-Driven: Authoritative for financial, contractual, and lifecycle milestone data, such as assignments, cost centers, locations, or purchase dates.
- CI-Driven: Authoritative for technical attributes from external discovery tools, such as operating systems, network addresses, or timestamps.
If you modify a value in a non-authoritative system, the synchronization engine overwrites the change. This overwrite maintains absolute alignment with your designated source of truth.
Protection Mechanisms
Automated protections prevent infinite update loops during bidirectional processing.
- Loop Prevention: The system tags changes when updating a CI. The Configuration Item Change Event recognizes this tag to clear repetitive cycles.
- Asynchronous Processing: Synchronization runs as a non-blocking process. If a single record fails, batch processing continues normally for the remaining items.