Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Coming in Fall 2019 release, Pulsar will have the ability to calculate roll-up summary fields offline.

You will need to have a minimum release of 2.3.x of the PulsarSettings AppExchange package.

Pulsar Settings Configuration

  • From the Pulsar Settings Manager tab in your org, click the Process Roll-up Summary Fields button.  This processing may take some time to create auto-generated Pulsar Settings encapsulating the data about your organizations roll-up summary fields.
  • Create a Pulsar Setting with key pulsar.rollup.enableRollUpSummaryFields and value set to TRUE
  • Due to processing constraints in mobile offline environments, by default Pulsar will perform roll-up calculations for 2 parent (master) generations.  In other words, if a child record is Created/Updated/Deleted, then roll-up summaries are recalculated for the immediate parent (master) records and the grandparent (master master) records.  If you wish to change this limit, create a Pulsar Setting with key pulsar.rollup.rollupParentLimit and value set to an integer number > 0

Limitations of offline Roll-up Summary Field processing

  • Validation rules on master objects are not triggered when performing roll-up calculations.
  • There is no way to perform a mass recalculation of roll-up summary values in Pulsar.  Pulsar will pick up new values from a mass recalculation initiated on SFDC servers during the next catch-up sync.
  • No labels