Skip to main content
GroupsCommons Project: DLRS
Featured group

Commons Project: DLRS

Declarative Lookup Rollup Summaries Tool, an Open Source Commons project. This group has been created to support discussion around this tool. This is a community powered tool so questions may not get answered immediately. Please post a screenshot of your DLRS record when asking for troubleshooting help =) In August 2021 DLRS joined the Salesforce.org Open Source Commons program to build community around this package. Joining the OSC helps ensure DLRS remains a trusted and sustainable open source package, that is free, community-led, and managed for years to come. If you'd like to contribute to DLRS, please post in the group!
Ask a question...
Hannah Wilshire (Litify/Salesforce Consultant at Banjaxed Solutions at Raphaelson & Levine)
May 13, 3:50 PM
Error when trying to deploy child trigger

 

i have installed the new version and am still getting the error:

Web service callout failed: Unable to parse callout response. Apex type not found for element testCategory

 

Error is in expression '{!checkAsyncRequest}' in page dlrs:managetriggermdt: (dlrs)

 

An unexpected error has occurred. Your solution provider has been notified. (dlrs)

 

 

The trigger still gets created but doesn't appear to be working

5 answers
Write an answer...
0/9000
Abdul Rehman Butt
May 19, 7:38 PM
I am running into an issue where this trigger dlrs.RollupService.triggerHandler(pse__Proj__c.SObjectType) is upadating a date field on Account object. How to check The UI Trigger Handler for thisdlrs.RollupService.
3 answers
  1. Anthony Heber (Valence Inc.)
    May 19, 8:38 PM

    DLRS has two places that it keeps configurations, the Custom Metadata are the "modern" way but if this has been installed in your org for a while you might also have some of the Custom Object variety. I would check both for possible configuration locations. 

     

    If it isn't present then it is more likely that DLRS is updating something else and triggering another automation, either on write to the Account object generally, or because of a specific field change. 

     

    If you use the Apex Debug Logs you won't be able to see the DLRS code running but if the update is happening outside of DLRS then hopefully you can see that occur and find the source.

Write an answer...
0/9000
Cheri Lovell (The Strategic Org)
May 15, 5:48 PM
Unable to connect/web service callout failed

I've used DLRS for years as System Admin, but today can't get past the Welcome page where I see a big red error banner (screenshot attached) — but no indications of what I need to fix. I've repeatedly clicked the Create/Update Remote Site Settings

button, but nothing happens. Since I was using version 2.17, I upgraded to 2.25 — but despite a successful install (per the email) I'm still getting the same error message. 

 

Besides the messages in the  banner, this message is shown below the

Create/Update

button — 

DEBUG USE ONLY: Web service callout failed: WebService returned a SOAP Fault: INVALID_SESSION_ID: Invalid Session ID found in SessionHeader: Illegal Session faultcode=sf:INVALID_SESSION_ID faultactor=

 

 

Any suggestions?

Screenshot 2026-05-15 at 1.44.26 PM.png
1 answer
  1. Anthony Heber (Valence Inc.)
    May 15, 7:57 PM

    @Cheri Lovell

    this could be a few things. Unfortunately that error doesn't help much, does it? 

     

    DLRS is attempting to communicate with the API using the Session ID from your browser, depending on the security settings in the org this may cause problems. INVALID_SESSION_ID suggests things are working well but the session Id used isn't enabled for talking to the API. 

     

    We have a new Beta wizard that should be available in the org, would you mind giving that a run? If you open the App selector and type "beta" it should come up. That is built using LWC components and uses different techniques to manage rollup records. The only thing you might still have a hard time with is if you need to add or remove child triggers (that still needs to talk to the Metadata API). 

     

    If you can give that a go and let me know if things work well in the beta wizard that might help us to narrow down where the failure is.

Write an answer...
0/9000
Steve Rossigno
May 12, 5:50 PM
Is it possible to see if there is a WHERE clause entered for a Scheduled Full Calculate job?

We are successfully running a daily Scheduled Full Calculate. 

When the scheduled full calculate job was created, an value was provided in the optional SOQL WHERE clause filter for the Parent object.  (eg.  only for Opportunities that are closed). 

We have multiple Scheduled Full Calculates running, which have been built over a number of years. 

QUESTION:  Is there somewhere we can see what SOQL WHERE clause may have been added for the existing Scheduled Full Calculate jobs? 

 

1 answer
  1. Anthony Heber (Valence Inc.)
    May 12, 5:59 PM

    @Steve Rossigno

    , there isn't anywhere in the DLRS app that would provide this right now. 

     

    It is oft-requested and pretty high on the proposed feature list right now. No ETA but I can say it will probably be worked on somewhere in the next few releases. 

     

    You might be able to pull it out of the Apex Debug Logs if you look at the SOQL queries used. You would need Apex Debug Logging enabled for the running user when the job starts. There will be a few transactions, one of them will hopefully include it in the SOQL_EXECUTE lines (If memory serves).

Write an answer...
0/9000
Alex Burns (Director of Technology at St John Associates)
Mar 18, 2:59 PM
Error message on trigger deploy after upgrading to 2.24

I upgraded to 2.24 and now I am getting an error message after deploying the trigger. 

 

Web service callout failed: Unable to parse callout response. Apex type not found for element flowCoverage

Error is in expression '{!checkAsyncRequest}' in page dlrs:managetriggermdt: (dlrs)

An unexpected error has occurred. Your solution provider has been notified. (dlrs)

 

It still seems to deploy the triggers successfully though.  

 

Error message on trigger deploy after upgrading to 2.24

 

 

8 answers
  1. Anthony Heber (Valence Inc.)
    Mar 18, 3:06 PM

    @Alex Burns thank you for sharing that. This was probably related to an API version update. I thought I was staying below where this was a problem but I'll have to dig in and see what is going on.

Write an answer...
0/9000
Nikki Myoraku (Salesforce Administrator at PVI)
May 5, 4:13 PM
Error on Manage Child Trigger when creating new DLRS

I am attempting to recreate a DLRS in production that I already successfully created in a sandbox. When I click 'Manage Child Trigger', I am receiving the following error (screenshot at bottom of post). 

 

The purpose of this DLRS is to count the number of related Payment Profile records to a Contact record. Payment Profile is a custom object from the Kulturra managed package and has an out-of-the-box lookup to Contact. I have created a custom number field on Contact called Has Payment Profile, to hold the results of the rollup. 

 

I noticed our DLRS version was 2.22, so I just upgraded to 2.25 and tried again, but still getting the same error. Also, not sure why I didn't have a problem with the same DLRS in the sandbox? 

 

Thank you!  

Error on Manage Child Trigger when creating new DLRS

 

 

1 answer
  1. Jon LaRosa (LaRosa Consulting)
    May 5, 5:00 PM

    Looks like you're going to need to write your own test class for the child object. Either that or disable the validation rule causing the issue, deploy the trigger, then re-enable the validation rule.

Write an answer...
0/9000
Harshal Kadam
May 6, 2:05 AM
Clarification on PKCE & Refresh Token Rotation Enforcement

Hi Team, 

 

We’ve received communication that Salesforce will be enforcing Proof Key for Code Exchange (PKCE) and Refresh Token Rotation (RTR)

as part of their ongoing security enhancements for all OAuth-enabled applications. These are mandatory Salesforce security standards that apply to all connected integrations.  

 

We would like to understand how this impacts our integration with your application.

Could you please clarify the following:

  • Do we need to take any action from our side to support PKCE and RTR?
  • Are there any settings that need to be enabled or updated in our Salesforce org or within your application?
  • Will these changes be automatically handled/updated from your end, or is coordination required?
  • Is there any documentation or timeline you can share regarding this update?

We want to ensure our integration continues to function smoothly without disruption.

Looking forward to your guidance.

2 answers
  1. Anthony Heber (Valence Inc.)
    May 6, 2:08 PM

    DLRS doesn't deliver or manage any Connected App or External Client App. The Salesforce security changes should have no impact on the operation of DLRS.

Write an answer...
0/9000
Charlotte Adkins
Apr 24, 10:18 AM
Deployed DLRS but received error message when trying to create a new opportunity record

Hello, I am hoping to use DLRS across 2 opportunity record types, which are related to each other via a lookup (they weren’t configured as master-detail). One record type we treat as if it’s the ‘parent’ and the other we treat as if it’s the ‘child’.  

 

The parent is the ‘head programme’ which contains the overall pot of money, and the child records are ‘sub-projects’ which technically are supposed to draw down from that pot. At the moment, users (i) create the record type ‘sub-project’ and add a £value to a Budget_c field on that page layout (ii) upon saving that record they return to the ‘head programme’ record type and manually deduct from the opportunity Amount field on there.  

 

Because our opportunity relationship isn’t master-detail, I’d like to use DLRS so we can say “the sum total of all the sub-projects is X” and paste that value into a custom field on the ‘head programme’ record type. I hope that makes sense?

 

This is what I’ve come up with so far:

Deployed DLRS but received error message when trying to create a new opportunity recordcustom budget field.jpg

I’d tried to add in opportunity record type ID = to either the object/relationship fields but was getting an error message when saving saying it didn't exist.DLRS first test.jpg

 

 

In the end I managed to save as above, but after deploying ‘manage child trigger’ , ticking the ‘active’ checkbox and saving, I then received this error message when trying to create a new ‘head programme’ opportunity. new opportunity error.jpg

This kind of thing in Salesforce is new to me and would be most grateful if someone could let me know where I’ve gone wrong please. Apologies if I’ve made an obvious mistake and can’t see it! Thanks in advance for any advice anyone may have.

2 answers
  1. Charlotte Adkins
    May 5, 7:45 AM

    Hi Anthony, thank you very much for coming back to me. You've summarized it correctly, this is what I am looking for - I must have misunderstood which fields needed to go in the relationship and aggregate, thank you for clarifying that. Really appreciate the help. 

Write an answer...
0/9000
Adam Vatterott (Nonprofit Consultant at Adam Vatterott Consulting, LLC)
Apr 21, 8:21 PM
Bypass validation rules?

Can DLRS handle the following scenario? 

  • User cannot edit a parent record "Contact A" because of a validation rule
  • User edits a child record "Engagement A" 
  • We want a rollup field (updated by DLRS) to update on Contact A to update based on the change to Engagement A. 
6 answers
  1. Anthony Heber (Valence Inc.)
    Apr 22, 9:44 PM

    @Adam Vatterott

    if the bulk calculations encounter a problem with a particular record then they log that error to the Lookup Rollup Summary Log object (dlrs__LookupRollupSummaryLog__c). 

     

    One log item per failed parent + rollup combination with the associated error. 

     

    If an error is encountered then that "Scheduled Item" record isn't purged and will be picked up again on the next run. It is useful to have a daily report for anything that is older than X hours old. Dependent on how often you run your processing job. That will let you see anything that is a persistent failure. (I think DLRS sends emails for some problems but I can't remember the details of when those are sent off the top of my head) 

     

    I usually recommend people schedule the processing job every 15 minutes but that takes four scheduled job slots (your org has 100 max) so some people opt for hourly, which is the most often you can do on a single slot.

Write an answer...
0/9000
Shruti Jain (Salesforce Administrator at Bucher + Suter)
May 1, 11:45 AM
Does DLRS work on formula fields?

I am exploring DLRS as an option to replace the existing setup I have in my org of 2 custom fields - 1 is a formula field, and 1 is field that gets updated with the value from the first but through a flow. This is done on say Opportunity Products so that on the Opportunity we can do a roll up of 'Total Price'. I would like to know if with DLRS this setup becomes any lesser cumbersome. 

Second question is if we can do a roll up on the grandparent using this tool. 

Thanks!

2 answers
  1. Jon Chen (RedPoint Solutions)
    May 1, 6:36 PM

    Roll-up summary fields work on Opportunity Products FYI. Won't help with grandparent rollups but still work considering!

Write an answer...
0/9000