Announcing the 2.18 Release for Declarative Lookup Rollup Summaries!

Declarative Lookup Rollup Summaries version 2.18 is out now! Version 2.18 is DLRS’s second release since it became a Salesforce.org Commons project. The last release was a relatively large face-lift with plenty of new bells and whistles. This time around, we’ve been focused on solving specific pain points and issues that you within the community have helped us to identify.

Here are some of the problems that this version aims to solve:

System Performance

The Dilemma

System performance has been an issue when it comes to DLRS, especially in more complex and mature Salesforce orgs. We had reports of hitting CPU limits, record-locking and other performance-based issues.

Let’s take a look at record-locking. When it comes to data management in Salesforce, “record-locking” can wreak havoc on our users. Record-locking occurs when automation or other processes, like DLRS, are occurring in the background and prevent users from accessing data on the parent record. DLRS was creating record-locking issues by running each time that updates were made on the child records, regardless of whether those updates actually made an impact on the value being calculated.

The Solution

DLRS now checks to see if the changes made to the child record will have an impact on the calculation. The rollup summaries only run if they need to, which uses up less system resources like CPU time and avoids some of the record-locking issues created by extraneous calculations. This greatly increases system performance!

Storage Space

The Dilemma

Storage space in Salesforce is precious. DLRS users were finding that their precious storage space for Scheduled Items was being eaten up quite quickly, especially when there were summaries that were no longer necessary or had been created, but not yet scheduled.

The Solution

We have now created a widget within the Lookup Rollup Summaries tool that will notify DLRS admins that the Scheduled Items are building up and either need to be scheduled or deleted. Now DLRS admins will have a better handle on the storage space being used by the tool.

Terminology and Field Labels

The Dilemma

Admins who are new to the DLRS tool found it difficult to figure out some of the terminology in the tool. These came from the field names that had been used since the tool was first created 10 years ago!

The Solution

We have updated the DLRS fields to better mimic the terminology used in the rest of the Salesforce platform. Just a few of the changes are:

• Lookup Rollup Summary name changed to Lookup Rollup Summary Label
• Unique Name changed to Lookup Rollup Summary API Name

Field creation has been streamlined as well, with the Lookup Rollup Summary API Name being auto-populated from Lookup Rollup Summary Label field similar to the way field creation works on the platform.

Full Release Notes

There are plenty of other smaller, but no less impactful items that have not been covered in this blog release. Check out the full release notes to learn about the bug fixes and other improvements that our amazing team of volunteers have provided, including some screenshots of the new functionality!

Thank you to our contributors!

Speaking of our amazing volunteers, we want to take a moment to thank the code contributors who have dedicated hours of time to make this release possible. The Declarative Lookup Rollup Summaries tool is part of Salesforce.org commons, meaning that our team is 100% volunteer-led. A big round of applause for our code contributors for Release 2.18:

• Scott Fenton
• Christian Szandor Knapp
• Anthony Heber
• Ezra LaFleur
• David Reed
• Jim Bartek

If you would like to find out more about the tool or get involved, head on over to our website.