Skip to main content
GruposCommons Project: DLRSPregunta de Archana Vijayakeerthi
Archana Vijayakeerthi ha preguntado en Commons Project: DLRS
3 jul, 2:51

DLRS Rollup Summary Issue – Resets Values Across Related Account Group

I’m running into an issue with DLRS rollup summary calculations involving a hierarchical account structure, and I’d appreciate some guidance.

Scenario:

  • I have two child Account records: 
    • Rob Family A
    • Rob Family B
  • Both are related to a parent Account: 
    • Rob Parent Family AB

Each of these accounts has multiple related Policy records. I’m using DLRS to calculate rollup summaries (based on a lookup relationship) to aggregate values from the Policy records.

Expected behavior:

  • Rollups on Family A and Family B should calculate independently based on their own related policies.
  • The parent (Rob Parent Family AB) should roll up the combined values from both children.

Actual behavior:

  • When I run the rollup on the parent account (Rob Parent Family AB), it resets the rollup values on Family A and Family B to 0.
  • Conversely, if I run the rollup on Family A or Family B, the parent’s value gets reset incorrectly.

Observation: It seems like the rollup process is overwriting or recalculating values for related accounts in the same hierarchy, rather than maintaining independent aggregates per record.

Questions:

  1. Is this a known limitation or expected behavior when using DLRS with hierarchical account structures and lookup-based rollups?
  2. Could this be related to how the rollup is configured (e.g., parent-child traversal, filter criteria, or calculation mode)?
  3. Are there recommended patterns to avoid rollup values being overwritten across related accounts in the same group?

Any suggestions on configuration or best practices would be greatly appreciated.

Thanks in advance!

1 respuesta
  1. Sai T (Raleigh Developer Group)
    28 sept, 8:23

    Hi Archana,

    DLRS normally calculates a rollup for the specific parent record returned by the relationship field. It shouldn’t reset sibling Account rollups simply because those Accounts share the same parent, so I’d first look at the configuration rather than treating this as expected hierarchical behavior.

    I’d check these areas:

    • Make sure the Policy → Account lookup used by each rollup is the intended relationship field.
    • Verify the Relationship Criteria / Filter so policies belonging to Family A and Family B aren’t being evaluated by the same rollup.
    • Check whether the parent rollup is configured to aggregate Policies directly or to aggregate the child Account rollup fields. Mixing these approaches can cause unexpected recalculations.
    • Review the Calculation Mode and whether multiple DLRS records/triggers are updating the same Account fields.
    • Run the rollups individually and check the debug/log output to see which Account IDs DLRS is actually recalculating.

    A clean pattern is usually to have one rollup for Policy → Account (giving each Family its own value), and a separate parent-level rollup that aggregates the intended child Account values. Avoid having multiple rollups write to the same target field.

    If you can share the DLRS configurations for the Family and Parent rollups (Relationship Field, Relationship Criteria, Field to Aggregate, Target Field, and Calculation Mode), it should be possible to pinpoint where the reset is coming from.

Escribir una respuesta...
0/9000