We are facing issue as DLRS rollups are not working at any level.
Object Hierarchy Requiring Rollups
Opportunity → Quote → Carrier_Quote_Coverage__c → Carrier_Quote_Details__c
Rollups Required Across All Levels
For each level, we have rollups for:
- Taxes
- Premium
- Fees
Specifically:
Opportunity:
Amount field (using Type__c picklist with values - Taxes, Premium, Fees)
Quote:
Amount field (using Type__c picklist with values - Taxes, Premium, Fees)
Carrier Quote Coverage:
Amount field (using Type__c picklist with values - Taxes, Premium, Fees)
Carrier Quote Details:
Amount field (using Type__c picklist with values - Taxes, Premium, Fees)
Issue
DLRS rollups are not working at any level. Previously, the lowest-level rollup (Carrier_Quote_Details__c → Carrier_Quote_Coverage__c) worked, but now even that is no longer updating. No rollups are firing in Realtime across the entire hierarchy.
What Has Been Verified
- All rollups are configured as Realtime.
- Lookup relationships are correct.
- DLRS child triggers are installed.
- No errors appear in DLRS logs.
The managed package is the standard Declarative Lookup Rollup Summaries package.
We need help to understand why all DLRS rollups have stopped functioning, including the lowest level, and determine whether this is due to platform behavior, trigger conflicts, or a DLRS package issue. We also need confirmation on whether DLRS supports cascading multi level rollups natively or requires additional configuration.
#DLRS #DLRS Package #Declarative Lookup Rollup Summaries
Thanks, @Rick C
! Full Calculate not working gives us something to start with. That takes a bunch of things out of consideration. Is it that nothing is changing or that the rollup value is wrong or that it is always leaving an empty field?
Remember, we're ignoring the realtime problem for now. It is almost always simpler to troubleshoot the Full Calculate, fewer moving parts.
After starting Full Calculate, are you applying any filtering on the start screen? (It gives you an opportunity for a WHERE clause to limit which parent records are updated)
Can you check the Setup => Apex Jobs page once you start the Full Calculate? You should see a RollupCalculateJob Apex class as a Batch job. It should have a number of batches with it. If you monitor that it should progress through all the records. Depending on the number of parents it needs to recalculate it might take a bit. Let us know how many batches it needed and roughly how long it takes from start to finish. (It should show the start and end times in the list view)
Will you check if it completes without any errors? If it encounters an un-handled error then it should report that error in the batch job's status. If it is a contained/handled error then it should email whoever started the job as well as add records to the Lookup Rollup Summary Log object.
I would start by watching the Batch job then if that looks good but still doesn't produce any results I would check the Lookup Rollup Summary Log object next.
Please report back if everything looks clean or if you find any obvious problems. You may need to look at the modified dates on those log objects to make sure you're dealing with recent outcomes.
