Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Asset Status Tracking Rules

            You are here:

            1. Salesforce Help
            2. Docs
            3. Agentforce IT Service

            Asset Status Tracking Rules

            To preserve inventory accuracy, review picklist configurations and background financial logging before changing asset status mappings.

            Required Editions

            Available in: Lightning Experience
            Available in: Enterprise, Performance, and Unlimited Editions with Agentforce IT Service.

            Picklist Value Modifiers and Deletion Risks

            Admins add custom configuration values to the Asset Status dynamic picklist to match organizational workflows. The system architecture relies on picklist values to calculate field-level rollups, including quantities in transit, on-hand counts, and allocations.

            • Configuration Integrity: Altering or removing active picklist values without auditing mapping dependencies disrupts data sync.
            • Asset Mapping Sequencing: To modify an infrastructure lifecycle phase safely, configure and activate new asset mappings in Setup before deprecating old picklist options. This framework prevents unmapped asset states and protects reporting tables from data corruption.

            Automated Ledger Records and Trigger Executions

            For locations configured for asset-based tracking, automated logic governs stock updates to maintain an accurate ledger trail.

            • Background Operations: When an asset changes phases, the system automatically adjusts the corresponding record details on the parent product item. The mapping sequence decrements the initial quantity and increments the subsequent quantity.
            • Transaction Records: The system automatically creates a ledger entry on the Product Item Transaction object with an Adjusted transaction type after an update completes.
            • Workflow Constraints: Rely on automated workflows for state changes to prevent duplicate balances or tracking discrepancies, and avoid manual entries on the transaction object.
             
            Loading
            Salesforce Help | Article