Make sure the user that is installing has the following permissions:
After that, on Setup, search for Connected Apps OAuth Usage. Look for
Salesforce.org MetaDeploy and select Install.
Next time you click on the installation link on the DLRS website, it should let you install.
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:
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
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.
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:
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
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
I'm only going to answer the first of these to come through. I'd recommend you delete this and comment on that other post from Rick C (DUAL) so that you can get updates.
There is no reason to post the exact same message under three accounts.
I am planning to enable the “Enforcing No-Argument Constructor on Apex Classes Used for Invocable Action Parameters” release update in PROD and would like to ensure that the DLRS
managed package complies with the requirements of this update.
So, could you please confirm if apex classes used for invocable action within your managed package have public no-argument constructors?
For example, the RollupActionCalculate class.
Thank you.
#DLRS #DLRS Packagelucky thing the code for DLRS is open and publicly viewable.
This is the only Invocable action in DLRS. It doesn't have any constructors on it at all. Reading the release notes it is not clear to me if that could be a problem.
https://github.com/SFDO-Community/declarative-lookup-rollup-summaries/blob/61d1cc9fb7d2c55ff9669302a659b962eb5abefe/dlrs/main/classes/RollupActionCalculate.cls#L48
As with most things, enable it in a Sandbox and confirm it behaves the way you want.
Ok, I was looking over the documentation more closely around the Relationship Criteria and Relationship Criteria Fields and I have a few clarifying questions. If I understand correctly, the relationship criteria field is where you put in what records you want included in your rollup. For example, on the child object if the "Engagement_Year__c != null, it would only include the child records where there IS a value in the Engagement Year field. Correct?
I know I am supposed to put Engagement_Year__c in the criteria fields, but why?
I have a couple of other questions about Watch for changes and a job specific scheduled calculation, but that's for another time.
#DLRS #DLRS Packagethanks, that makes sense.
I had an issue last night where like 11,000 rollup up summary log records caused an issue with another process and trying to figure out why. (well I know part of the answer, but still trying to figure out the rest, as issue has got to do with a managed package that is still using a PB that I can't "see", so I don't know what's causing that to fail, which in turn is impacting the rollup. It's never happened before, so I am guessing the vendor made an update which is causing issues....) And I am making sure that some of my early rollups I made, make sense...
Hi everyone,
I'm inspecting our rollups and finding some DLRS calculations that I need help understanding a few things.
My first question is: does a DLRS need to be active in order to run? I'm seeing that all of ours are not active, and the ones that are scheduled do not have a future schedule date. Does this mean they were somehow switched off and I just didn't know about it?
My second question is: can you run DLRS referencing the fiscal year instead of the calendar year? Things like this fiscal year, last FY, FY 2 years ago…etc. If so, what's the notation for this?
My third question: is it a problem if the "ID" part of one of the relationship criteria points to a single record in Salesforce? Or is this the notation for the DLRS updating only each single fund with it's respective children? Or something else? Here is the criteria for the DLRS in question, salesforce Id obfuscated with 'singleSFId':
Amount__c != null
AND
FmlStatus__c in ('Closed','Cancelled','Declined','Executed')
AND
FpApprovedDate__c = LAST_N_YEARS:2
AND
id = 'singleSFId'
Thanks for your help,
#Salesforce Developer #Flow #DLRS SOQL #DLRS
You can't move the scheduled Apex jobs from SB to Prod. You'll need to re-create them
Hi Everyone,
I hope this message finds you well!
Could someone please share the latest version of the DLRS installation package? Is it 2.23 or 2.9? Additionally, I would be grateful if you could provide the most recent production and sandbox URLs.
Any Help is Much appreciated.
#DLRS #Salesforce Developer #Salesforce AdminThe most recent version is 2.23 (two point twenty three) - you can find the install details on the install page on the DLRS Documentation Site. If you want the direct URLs you can find them on the DLRS GitHub site most recent release.
Quick question, I know that the Beta view of the rollup summaries, shows more information, like Parent, Child, Aggregate Result Field and more. I was wondering if there are any plans to allow us to create custom list views? Or is there a way to create Custom Report Types to get to the same information, but a bit more grainular? Like showing by Child Object, etc? I am working on documenting my org and for regular rollup jobs, I can use the data type to see if a field is a rollup or not, however, using DLRS, you are creating "regular" fields and while I have started noting it's a rollup in the description, I am looking for an "easy" way to find what other fields I need to tag. I am using the new Rollup List view field, but was just curious if we could use reports. I did try, btw, but no results showed up.
#DLRS #Nonprofit #Salesforce Admin
@Anthony Heber and @Jon LaRosa Thanks, I appreciate the insight. I remembered that DLRS went to metadata, and I just did not make the connection that I would not be able to create reports. Although it would be cool if SF could make that happen...I mean metadata is Data, too....
Ok, I know this has been asked before, and I read a couple of responses, however, I want to make sure I understand the underlying issue correctly. I am seeing this warning stating that I have 2467 scheduled items. See the screen shot.
I saw a couple of post stating that I need to schedule the Rollup Job to clear or run any items that failed, etc. And I saw
this post by @Shari Carlsontalking about the differences in scheduling prior to 2.21. However, I am on 2.22 (and I am not sure when I updated or how long that warning has been there, to be transparent). I also don't see items in my Summary Logs (but again, it's possible I deleted those).
So my question is, do I just need to schedule the Rollup Job to just run a couple of times a week to "clear" out these items? Part of my confusion is that I do have 9 rollups scheduled to roll up nightly and those appear to be running fin, no errors, etc so I just want to make sure I am doing the right thing. I also noticed that there are too rollup jobs I can select "Rollup Job" and RollupCalculateJobSchedulable so I want to make sure I am scheduling the right one. And just to add to my confusion, in Apex Jobs, I just noticed that there is a scheduled apex that was created on 4/2/2025 (it looks like and has NOT run... (see below) So again I am just a bit confused.
#DLRS #Lookup Rollup Summaries #Nonprofit #Salesforce Admin
"Watch for changes and process later" in the new wizard is the same as "Scheduled" mode in the old wizard. These options are for "install the trigger and watch records as they change but don't recalculate the value for the parent right away" instead it enqueues records into the Scheduled Items bucket which are drained by the "RollupJob" at a future time. But only if you are actually running that job.
These are completely separate from the "Schedule Full Calc" jobs. So if you have anything that is currently set to "Scheduled"/"Watch for changes and process later" then you need to be running the "RollupJob" to process those enqueued items. If you ONLY use the scheduled calculation then you should be able to put them into "Process Builder" mode (which doesn't use the triggers and doesn't automatically watch for changes) and your scheduled jobs will take care of it all. In that case you can just delete those items and everything will be good to go (because you're ensuring the values are updated through your scheduled full calculates)
One note, those items can be created by some rollups if the parent can be merged, there is an edge case behavior where merging a parent will create scheduled item records. So it is probably a good idea to always have the "RollupJob" class scheduled even if you don't expect it to do any work.
Again, if you need the Scheduled Items processed then follow Shari's instructions to get that job added. This is totally separate from the "Full Calculate" jobs that you have scheduled.
I hope that is more clear.
I am including a number of screenshots. I recently updated to the latest version of dlrs, and have since been having some issues. I am getting daily emails informing me of a failure for a rollup that isn't even supposed to be running anymore (is inactive). It reads:
Error: A calculate job for rollup 'Sum Last Year's Gifts on RD' is already executing. If you suspect it is not aleady running try clearing the applicable record from the Lookup Rollup Calculate Jobs tab and try again. Review the error, rollup definition and/or delete the Apex Scheduled job under Setup. Check if the rollup still exists via the Manage Rollup Summaries and/or Lookup Rollup Summaries tabs.
The 'summaries tool' tab shows some warnings in the 'optimizer' that I've never seen before (see first screenshot). I follow the directions, checking the logs (screentshot 2) and confirming that nothing has 'broken' since 2022). I see the fields in screenshot three in this custom object that is part of dlrs, and I select 'edit' from the dropdown of the 'old' (dlrs__LookupRollupSummary__c) field, to find that it is not possible to remove the field I am told is no longer necessary. See field settings in screen shot 4, and perhaps someone out there who has used this tool can point out my error to me.
#DLRS
#Lookup Rollup Summaries
I think there are several things going on so let's take them one at a time - starting with deleting the no longer needed field.
First, deleting the no longer needed field. Here's the
FAQ item that covers this issue. There are a few steps that you need to take including review and deleting any scheduled items that reference that field before attempting to delete. In Lightning, you don't need to open the field to delete it, you use the dropdown at the end of the field row in the Field & Relationships tab. But I think I have always needed to switch to Classic to delete this field. (Let me know if you need help finding/deleting the field in Classic).
Let me know if you still have issues deleting that field. Once we get that field deleted we can jump to the next issue. Also if it would be helpful to jump on a call, feel free to direct message me and we can find a time.
