Salesforce Formulas
Spring 2019 Note: Pulsar now directly supports evaluating Salesforce formulas both online and offline.
...
- If there is both a Salesforce formula and a Pulsar Settings Langugae (PSL) formula (see below) for the same field, the PSL formula takes precedence, and the Salesforce formula is ignored
- Salesforce formulas and PSL formulas across objects/fields should not interact (e.g., if FormulaFieldA__c is a Salesforce formula and FormulaFieldB__c is a PSL formula, the result is undefined if they reference each other).
- Formula fields are calculated on-the-fly every time you view a record detail page (but not when editing)
- Currently due to processing limitations, formula fields are NOT calculated in list views. Stale values may be shown in list views unless steps are taken to persist calculations (see below).
Offline persistence of formula field
...
calculations
By default, due to inherent processing limitations, formula field calculations are not persisted to the local database when offline.
This is often not a problem for organizations for various reasons. For many organizations, user interactions with formula fields are usually only ever interacted with when on record detail pages (where these formulas are always dynamically calculated). Furthermore, formula field calculations are synced from Salesforce servers and persisted to the local database when online during record creation and updates, or when Pulsar next syncs those offline created/updated records. When online , or syncing there is always a readback that picks up server-side calculations.
But for some organizations, when running offline in Pulsar, the lack of persistence of formula field calculations can present a problem. This is usually due to happens in the following two scenarios: (1) formula fields present in list views, and (2) customizations that directly query formula fields from the database (e.g. querying via PSL or via the Javascript API).
...