How To Update Declarative Rollup Summary Tool To Existing Records

I typically practise not web log near each new release of this tool, just since its been awhile and at that place is some key features in this release I idea I would add to the usual release notes. If you are not aware this is a customs driven tool that helps address a electric current platform limitation around rollup summaries. Specifically the disability to practice rollup summaries between lookup relationships. This is possible between master detail relationships using the declarative style of Lightning Platform, simply not between Lookup Relationships. The tool is open sourced and supported by an amazing community! The post-obit highlights some key aspects of this contempo update.

Improved Lightning Experience Support

The tool does its thing in the background as users work so regardless if you configure it through Salesforce Archetype or Lightning Experience, for your users it is irrelevant. This release has an actual Lightning App packaged with it and each of the custom UIs at present leverage the default Visualforce Lightning styling. Yous can even so use it in Classic, though the new Lightning Rollup Summaries Tool tab will not be visible.

welcome

Evolution of Rollup Configuration Storage

The tool has been around since 2013 and has undergone some changes, particularly since the advent of Custom Metadata, which is at present the chief ways past which its configuration is stored. Support for the original Custom Object based storage of configuration is all the same present but is now more hidden past default to avoid confusing new users. This release includes more messaging in the older UI to help users tell the deviation. Unfortunately some legacy implications however confused users which I besides wanted to accost in this new release.

warning

No More than Shadow Rollup Records

Scheduled rollups can leverage an incremental adding mode to differ calculations until a scheduled batch job executes, which improves interactive performance. The tool does this as the users update records by inserting into the Lookup Rollup Summary Schedule Items object to queue upwardly the future recalculations. This object was architected before the Custom Metadata based rollups and thus demanded a reference to a Custom Object based rollup even if the user was using the Custom Metadata based rollups.

Previous releases of the tool attempted to workaround this silently by automatically creating and so called "shadow rollup" configurations. All the same when users came across these, particularly if they where nonetheless using Custom Object based rollups, it acquired confusion. Starting with release v2.12 these will no longer be created. Though for those of you upgrading there is some actions to take on your side.

shadowrollup

Action to Take and New Lookup Rollup Summaries Tools Tab

In order to drib the confusing shadow rollup workaround described above I had to remove a field from the Lookup Rollup Summary Schedule Items object. This notwithstanding is only removed from the package and will not automatically delete from orgs on package upgrade. I take ensured that your existing rollups will still piece of work and however leverage this field, so there is no firsthand action subsequently upgrading.

However, if you create a new incrementally scheduled rollup and endeavor to insert a child record you will see the error message that reminds you need to delete this field manually. Y'all will also run into a reminder to delete this field through the new tools tab.

optimizertool

As yous can run into above the new Optimizer component is also designed to share other useful insights into your use of the tool. In add-on to the field deletion reminder I have too added a notification to remind the admin to review the Lookup Rollup Summary Log tab for errors that have occurred during incremental scheduled rollup executions. Each of the notifications comes with a more detailed Wiki page. Once everything has been cleared you go a nice confirmation telling you so!

allgood

Email Notifications for Batch Job Fault Letters

The tool uses scheduled Apex jobs to run manual total, scheduled full and incremental recalculations of rollups. For incrementally recalculations expected errors get redirected to the Lookup Rollup Summary Log tab (hence the in a higher place reminder in the tools tab). Even so other errors in previous releases where just visible if you visited the Setup bill of fare Apex Jobs folio or had Apex E-mail Notifications enabled. Starting with release v2.12 such errors (unless they are governor limit errors) will be emailed to the user who scheduled the chore.

No Need for Remote Site Configuration

Finally I as well updated the tool to leverage a platform enhancement that relaxed the demand to have a Remote Site configuration when using Salesforce API's such as the Metadata API used by the tool when configuring rollups. This just applies to orgs with My Domain.

Customize Test Code for Parent Apex Trigger Tests

Sometimes the tool needs to generate Apex Trigger Test code for parent objects. In this release you can now customize that test lawmaking if at that place are required fields needed to be able to insert a examination parent object.

testparent

Future Releases

There is currently 82 enhancement ideas and 22 known bugs to choice from. If you want the perspective on must take fixes and enhancements from ane the astonishing contributors, Dan Donin, yous can run across Dan'southward filtered list hither.

Hopefully having moved the projection to SFDX you or a developer y'all know will feel encouraged to help out with some of these. I am also keen for ideas on how to enhance above optimizer feature to provide more proactive recommendations to admins and cut down on mutual questions and continue configurations optimum.

Finally there is a long standing asking for UI to help configure the rollup filters that might finally be closer to reality thank you to some great piece of work here. Meanwhile, thanks for all for the back up!