Is there any additional configuration required beyond adding a custom Account field to the cgcloud__MobilityRelevant field set to make it available for PPP calculation in the offline app?
1. Sync the Field to the Local Database:
Add the custom Account field (e.g., Distribution_Channel__c) to the cgcloud__MobilityRelevant field set on the Account object in Salesforce. This ensures the sync engine downloads the field from Salesforce to the offline app's local SQLite database.
2. Define the Pricing Context and Key Attribute in Salesforce
In the Salesforce org, create a Pricing Context Definition and define a Field Alias for your custom field. Next, create a Key Attribute record. Set the Object to Customer, the Mobility Entity to Customer, and enter a value in the Mobility Attribute field that exactly matches the Field Alias you just defined.
3. Update the Offline Pricing Data Source in CG Cloud Modeler
Open the Consumer Goods Cloud Modeler workspace and check out the offline pricing data source contract named DsComplex_Pricing_sf. Locate the CndCpReadCustomerAttributes query within this contract and add your custom field (Distribution_Channel__c) to the SELECT statement.
4. Map the SQL Alias
In the CndCpReadCustomerAttributes query, you must set the SQL alias for your custom field to exactly match the Field Alias/Mobility Attribute you defined in Step 2. (Example: Account.Distribution_Channel__c AS YourExactAliasName)
5. Build, Validate, and Deploy
After updating the modeler configuration, build the code (sf mdl build) and validate the pricing behavior using the Modeler simulator. Once validated, generate a new Deployment Package and assign it to your users so the updated contracts are pushed to their mobile devices during their next sync.
005386003

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.