System Numbers in Retail Execution

Available in: Lightning Experience in Professional, Enterprise, and Unlimited Editions that have Consumer Goods Cloud enabled.

Two properties make system numbers special. First, the device generates them fully offline, so field users can create and number records with no connectivity. The server doesn't assign numbers later. Second, different devices never collide. Each device embeds its own identifier in the number, so two devices that number records at the same time still produce different numbers, and each device counts its own records upward.

The app assembles a system number from ordered segments, such as a fixed prefix, the device identifier, and a running counter, based on a system number definition that you configure in Salesforce. Your configuration controls which segments appear.

A system number relies on these key objects.

• System Number (cgcloud__System_Number__c): Defines the overall template, sales org scope, active status, and fallback logic.
• System Number Segment (cgcloud__System_Number_Segment__c): Defines individual components, such as sort order, lengths, pre-delimiters and post-delimiters, and counting systems.
• System Number Last (cgcloud__System_Number_Last__c): Tracks the last used counter value per device and per number definition.

Note: Uniqueness across sync sessions isn't automatic. Each device must upload its counter progress to the server. If a device advances its counter but doesn't sync that progress before you reinstall or restore the device, the device can resume from an older counter value and reissue numbers it already used, which creates duplicates.

• How a System Number is Built
  The app lays the segments out from left to right and fills each one according to its type. A definition contains only the segments you add to it, in the order you choose. A definition can be as simple as a single counter, a prefix and a counter, or it can also include the device identifier and more.