Documentation

Install it.
Then operate it.

Everything needed to take a package from install to production, written for the admin who has to run it.

Install, configure, and operate rollups in a production org.

Install

Install Ditto Rollups from the AgentExchange listing. Choose Install for Admins Only unless you already know which profiles need it. The package contains Apex and LWC only: no external callouts, no remote site settings, and no connected app to authorise.

Screenshot coming soon

Assign permission set

Assign Ditto Rollups Admin to whoever maintains rollups, and Ditto Rollups User to anyone who should read the values. The app is gated on custom permissions, so profiles stay untouched. API and Data Loader saves need the same permission set on the integration user.

Screenshot coming soon

Open the app

Find Ditto Rollups in the App Launcher. It opens on the Rollups tab, which lists every rollup in the org with its parent object, child relationship, function, and current state.

Screenshot coming soon

Create your first rollup

Click New Rollup and pick the parent object, then the field that should hold the summary. Choose the child relationship, the field to aggregate, and the function. Add filter criteria if only some child records should count. Nothing calculates until you activate the rollup.

Screenshot coming soon

Deploy the trigger

Activating a rollup generates one Apex trigger for the parent object and deploys it through the standard metadata API in your org. Run the initial calculation to backfill existing records before you rely on the values.

Screenshot coming soon

Hourly recalculation

Turn on hourly recalculation when changes can arrive without firing the trigger: data loads with triggers disabled, API updates, or time-based criteria. The scheduled job appears under Setup → Scheduled Jobs and runs inside your org.

Screenshot coming soon

Error log

Every failed recalculation lands on the Errors / Logs tab with the record id, the rollup name, and the exception. One failure never blocks the rest of the batch, and nothing fails silently.

Screenshot coming soon

Kill switch

In Settings, switch rollups off. Every trigger returns immediately and no DML runs, which is what you want before a large migration. Switch it back on and run a recalculation to reconcile.

Screenshot coming soon

Uninstall

Deactivate every rollup, then uninstall the package from Setup → Installed Packages. Fields created for rollups remain on your objects, so delete them yourself once you are sure the values are no longer needed.

Screenshot coming soon