Use this link to share with your colleagues:
Installing the Declarative Lookup Rollup Summary Tool: https://help.pm.leapevent.tech/a/1060020
Installing the Declarative Lookup Rollup Summary tool - also known as DLRS - has an additional step besides just installing the App. And, because it's so powerful, its power could also break essential functions in your PatronManager account.
In this article, we'll...
- Install DLRS in your sandbox
- Fix the Salesforce Metadata API error if it arises
- Build the rollup you've been dreaming up
- Test to make sure nothing has been broken by your rollup
- Install DLRS in your production account
The app installation process should take about 30 minutes, and the testing and migration of any created rollups may take between one to two hours.
Let's go!
To help set you up for success, we’ve put guidelines together to help you avoid interfering with PatronManager functionality, corrupting your data, and to prevent negative impacts to your customizations due to PatronManager product upgrades.
Before we begin, a word of caution:
DLRS is truly fantastic and completely yours to own. But, when used incorrectly, DLRS can and will break essential functions of PatronManager. You'll need to exercise caution, follow our guidelines below, and test out each rollup you build in a Sandbox before you deploy it in your production account. The power - and the responsibility - are in your hands.
1. Installing the DLRS Package
We've got our prerequisites out of the way, so lets....
1.1. Make sure you're logged into your sandbox
1.2. Install the latest DLRS version
Follow the instructions at the link below to install the app.
Here's where to find it: https://sfdo-community-sprints.github.io/DLRS-Documentation/Installation/
2. The Salesforce Metadata API connection error
It's possible that the following error could appear after your installation:
"Salesforce Metadata API connection failure, click the link below to configure."
Luckily, this is an easy problem to solve. Let's walk through that process.
2.1. Click on "Setup"
2.2. Search and click on "Remote Site Settings"
2.3. Click "Edit" next to the dlrs_mdapi site
2.4. Get your domain/server
We've got a whole article about finding that out.
2.5. Update the Remote Site URL with your Salesforce server/ domain. When that's done, click "Save"
Your URL will look something like one of these two examples:
https://wonderfuled--dlrs.vf.force.com
https://cs24--dlrs.vf.force.com
2.6. All right, error solved!
3. Build your rollups
Now that you've installed the app, you can begin experimenting with it! You can find further instructions on using the app here, but there are a few additional guidelines to follow since you're using the app alongside PatronManager. We'll show you what not to do below.
DLRS and PatronManager: important guidelines
Be careful, ignoring these warnings could break PatronManager and prevent you from selling tickets and processing donations.
3.1. Use only "Process Builder" calculation mode
This means no real-time rollups, as the trigger required to use those can interfere with PatronManager functionality. Instead, you'll set the Calculation Mode to "Process Builder" and then set up the schedule manually.
Q: I see a Calculation Mode called "Scheduled", shouldn't I use that to schedule it?
A: No! While the "Scheduled" Calculation Mode sounds right, that mode requires a trigger and that can break things in PatronManager. Expand the instructions below to see how to schedule your rollups to avoid this issue.
Set the Calculation Mode on your rollup to "Process Builder":
Q: Wait, does this mean I have to set up Process Builder, too?
A: Nope, don't worry! While the "Process Builder" Calculation Mode would allow you to trigger your rollup via Salesforce's Process Builder tool, you don't have to -- it's just a mode that avoids particular issues with triggers.
Once you've saved your rollup in Process Builder mode, you'll click the "Schedule Calculate" button to set it to run automatically on a daily basis:
The default settings will recalculate the rollup daily at 2am; you can adjust that if needed, then click "Schedule Recurring Calculate Job"
That's it!
3.2. Do not deploy any triggers
If you set the Calculation Mode to "Realtime" or "Scheduled" you'll see a message telling you to deploy a trigger before you can activate the rollup, but those triggers can break PatronManager. Instead, follow the instructions above to schedule your rollup in "Process Builder" mode.
Click "Manage Child Trigger"
Scroll to the bottom of the page and check which button appears on the left
You'll see one of two things; either a button to "Deploy" the trigger, or a button to "Remove" it. Here's what to do in each case:
Click it!
Scroll back to the top of the page...
You should see a message that the trigger is being removed (though it'll look like nothing is happening):
Wait for the page to reload
After a short wait (seconds to a minute or two), the page should reload with a message that the removal is complete:
All done! Scroll to the bottom of the page and click "Cancel" to return to the rollup page.
Great! That means you don't have a trigger, so you're all set here. Do NOT click the "Deploy" button.
Click "Cancel" to return to the rollup screen:
Need additional help? A great resource for troubleshooting your DLRS rollups is this Trailblazer group, filled with DLRS and other Salesforce users.
4. Testing your rollups
You've built a rollup - hooray! Now, you need to do some testing to make sure it plays nicely with PatronManager and doesn't cause things to break.
We have a full list of tasks you should perform to make sure your rollup doesn't interfere with your day to day operations here.
5. Installing DLRS in production
Now that you've installed and tested everything in a sandbox, you're ready to move onto your production account. This is a three step process...
5.1. Install the app in production by working through steps one and two above
5.2. Migrate your specific rollup by adding the Lookup Rollup Summary component to a change set and deploying it to production
Learn more about building and deploying change sets here.
5.3. Test the rollup again in your production account to double check everything in your PatronManager account is still functioning correctly
Here are our recommendations on testing rollups. To test transactions, you'll need to use a real credit card of some sort. If you're comfortable with using your own, do so. If not, you can ask the top brass at your organization to get a credit card for you to use for testing.
Either way, you'll refund the transactions immediately after making sure everything is working correctly. We recommend setting ticket price levels to relatively small dollar amounts.
Untested rollups can break PatronManager's ability to sell tickets and take donations.
- Test each new rollup in a Sandbox before bringing it into your production account
- Test all your rollups in that Sandbox after each new PatronManager release
- Once you move your rollup over to production, test it there as well
