---
schema_version: "1"
id: dceac526f4c1aad0da54222ce9c0090e28a05347c2c9452dd1ddd10fcd16f11c
title: IT Asset and Configuration Item Synchronization
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/it_srvcs_asset_mgmt_track_activity.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.it_srvcs_asset_mgmt_track_activity.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 41dec0f5c63bb67da2a3d1f4147566bb60fade3970531c611f4aa71e6dc9e244
description: Synchronize your IT hardware assets and configuration items to maintain data consistency across tracking environments.
products:
  - Service Cloud
  - Agentforce IT Service
release: "264"
---
# IT Asset and Configuration Item Synchronization

Synchronize your IT hardware assets and configuration items to maintain data consistency across tracking environments.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> Editions with Agentforce IT Service.</td></tr></tbody></table>

Automated bidirectional updates eliminate manual reconciliation and ensure your IT reps work with accurate records.

## Operational Precedence and Source of Truth

To coordinate dataflow without creating duplicate records, synchronization uses field mapping and field-ownership rules. Every mapped field connects with a single designated source of truth. The asset repository or the configuration management database (CMDB) defines which platform takes precedence.

## Recommended Authoritative Field Mappings

Field ownership configurations align with the operational strengths of each data repository.

  
| Data Category | Authoritative Platform | Operational Fields and Sourcing Impact |
| --- | --- | --- |
| **Financial & Contractual Lifecycle** | Asset | Tracks asset procurement, financial depreciation, and ownership assignments. Mapped values include **Assigned To**, **Cost Center**, **Location**, and **Status**. |
| **Technical & Operational Discovery** | Configuration Item (CMDB) | Tracks properties discovered through network scanning. Mapped values include **Hostname**, **IP Address**, **Operating System Version**, and hardware parameters. |

## Infinite Loop Prevention

Because modifications flow bidirectionally between records, updating an asset can trigger a configuration item modification. This change publishes a platform event that updates the asset record again.

To prevent infinite update loops, the framework uses explicit source attribution rules. When a change originates in the repository, the outbound synchronization engine tags the update with a tracking identifier. If the engine detects this self-originated tracking tag, it drops the event. This action breaks the background processing cycle.

When the configuration management system processes the update, the system maintains the source indicator string. The framework continually evaluates incoming payloads. If the engine detects the tracking value, it identifies the transaction as self-originated and drops the event.

## Sync Log Audit Structures

System warnings and transaction errors populate the Configuration Management Item Sync Log (`CnfgMgmtItemSyncLog`). These entries provide clear troubleshooting metrics directly in the setup console and eliminate inspecting raw engineering data.

## Key Fields for Troubleshooting and Auditing

Each log entry exposes essential operational metadata to isolate synchronization issues:

- **Log Title**: Shows a high-level summary of the transaction status.
- **Log Description**: Provides granular error data, delta properties, and suggestions for resolution.
- **Status**: Identifies the context category, such as **Success**, **Warning**, **Error**, or **Action Required**.
- **Related Object and Configuration Item ID**: Links to the specific asset record or unique identifier causing the mapping conflict.
- **Log Timestamp**: Shows an immutable marker of the exact date and time that the event occurred.

## Common Synchronization Exceptions and System Outcomes

Reps frequently encounter these synchronization scenarios during system updates:

- **Multi-Asset Matches**: If a discovery scan maps an incoming configuration item to multiple asset records, the framework halts the transaction. The engine generates an alert instructing the admin to resolve duplicate records.
- **Missing Mandatory Fields**: If an incoming event initiates creation of an asset record but lacks required attributes, the engine creates a locked asset shell. The log sets the status to **Action Required** to prompt manual remediation.
- **Unmapped Picklist Values**: If an operational state changes within the configuration management database, but the text value lacks a defined translation rule, the engine skips the update. This path preserves asset record data integrity across both systems.

#### See Also

- [View an Asset's Lifecycle History](https://help.salesforce.com/s/articleView?id=service.it_srvcs_asset_mgmt_view_lifecycle.htm&release=264.0.0&type=5 "Track the complete chronological journey of an IT asset. Maintain an accurate audit trail and preserve a clean chain of custody. The asset timeline records significant events directly on the asset record. These events include fulfillments, returns, and stockroom transfers.")