Loading
Table des matières
Sélectionner des filtres

          Aucun résultat
          Aucun résultat
          Voici quelques conseils de recherche

          Vérifiez l'orthographe de vos mots-clés.
          Utilisez des termes de recherche plus généraux.
          Sélectionnez moins de filtres pour élargir votre recherche.

          Recherchez dans toute l’aide de Salesforce
          Asset Status Tracking Rules

          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.
           
          Chargement
          Salesforce Help | Article