Quick Start Guide for Setting Up Declarative Lookup Rollup Summaries in Salesforce
Вставка
- Опубліковано 26 лип 2024
- Declarative Roll-Up Summaries (DLRS) is one of the most powerful tools every Salesforce org should have installed. It is free, open source and keeps getting better and better.
In this video, we will show you how to install DLRS and setup your first roll up in minutes. We show you how to create a field on the Contact that will show the # of closed won opportunities the Contact was related to via the Opportunity Contact Role record.
Link to Install DLRS: install.salesforce.org/produc...
Link to How to Article from Blu Ninjas: bluninjas.com/how-tos/cheat-s...
Here are some of DLRS's capabilities to make you look like a #salesforceadmin hero:
1. Rollup Data: You can easily roll up and display aggregated data from child records to parent records. For example, you can calculate the total revenue from the current year from all related opportunities and display it on the account record, providing a comprehensive overview of the account's financial performance.
2. Counting Records: DLRS enables you to count the number of related records and display the count on a parent record. For instance, you can track the number of cases associated with an account, giving you insights into the account's support and service history.
3. Calculating Averages: You can leverage DLRS to calculate averages from child records and surface the average value on the parent record. For example, you can determine the average rating of all associated customer reviews and display it on the parent record.
4. Finding Minimum and Maximum Values: DRS enables you to identify the minimum and maximum values from child records and display them on the parent record. This can be helpful when tracking important metrics like the minimum and maximum order value for an account.
5. Summarizing Custom Metrics: If you have custom metrics or key performance indicators that need to be calculated and displayed on a parent record, DLRS can handle the aggregation and presentation of these metrics. This allows you to have real-time insights into important data points without relying on creating reports.
6. Building Hierarchical Rollups: DLRS allows you to perform rollup calculations across multiple levels in a hierarchy. For example, you can calculate and display the total revenue for a parent account, including all child accounts and their associated opportunities.
CHAPTERS:
---------------------------------------------------
0:00 Intro
1:22 Install DLRS Package
2:52 Create New Field for Rollup on Contact
4:18 Create Rollup in DLRS for Closed Won Opps
8:25 Trigger Update to Existing Records
9:05 How to View Apex Jobs
9:36 How to Schedule a Rollup to run
10:30 How to View Scheduled Jobs
12:26 Create Another Rollup
12:56 Create Formula Field for Amount on Opportunity Contact Role object
14:20 Create New Field for Rollup on Contact
15:39 Create Rollup for Amount Closed Won Opps
17:33 Add Filter to Rollups to Show Closed Won Opps for This Year
19:05 Use Developer Console to Query Opportunity Contact Role Record
20:42 Update Rollup to have Year Filter
21:57 DLRS is only triggered when Child Record is modified
25:12 Wrap-up
About the Moderator: Cheryl Fernandes is a certified Salesforce Architect with 12 years of experience working on the Salesforce platform with a focus in the insurance and financial services industries. Despite not having an IT background, Cheryl found herself becoming the accidental admin at her previous company, and it turned out to be a life-changing opportunity.
Fueled by her passion for Salesforce and the remarkable transformations it can bring, Cheryl took a leap of faith 7 years ago and started her own consultancy, Blu Ninjas. As a registered Salesforce partner, she has been providing exceptional services and solutions to clients, while continuously honing her expertise in the Salesforce ecosystem.
Now, Cheryl is on a mission to inspire and empower Salesforce professionals worldwide through Blu Tiger Academy. Let us know what you are interested in, what business problems you cannot solve and what you would love to learn more about.
Follow us on LinkedIn and check out our website for other how to articles:
LinkedIn: / fernandescheryl
Blu Ninjas on LinkedIn: / blu-ninjas
Blu Ninjas How To's: bluninjas.com/how-tos/
#salesforce #salesforceadmin #salesforceohana #salesforcetrailhead #salesoperations #salesforcedeveloper #einstein #salesforcetutorial #salesforcetutorials #salesforceturotials #salesforcetraining #salesforceadministrator #salesforcetips #dlrs #salesforcedevelopment - Наука та технологія
Thanks for sharing, this is a powerful and underrated tool!
You're very welcome!
Informative and useful, thank you!
You are welcome!
Amazing as usual!
Thank you, we appreciate you!
Hello Cheryl, congrats for this video, it was truly impressive. Your expertise shines through, and I've gained valuable insights.I'm reaching out because I'm currently working for an EdTech company, and I'm eager to implement a similar approach to calculate district penetration. Specifically, I want to count the schools under a parent account with the Account Status set to "Active." I believe Declarative Lookup Rollup Summaries can help me achieve this, but I've encountered a challenge. In your tutorial, you demonstrated the process using different objects (Contacts as the Parent Object and Opportunities as the Child Object). In my case, I need to perform this calculation with both objects being Accounts. However, I've run into unexpected issues, and it doesn't seem to work as intended. I was wondering if you've ever encountered a similar scenario or if you could guide me in the right direction to adapt the process for my use case. Any insights or advice you could provide would be immensely helpful.
Thank you in advance!
Thank you so much for the kind words!! This is a great question!
I mocked up your scenario in my developer sandbox and let me know if this sounds correct. You have a Parent Account and you have multiple schools related to the Parent Account via the ParentId field. Then you want to count the # of schools with Account Status = Active under the Parent Account and update a field on the Parent Account to show the # of Active schools. If this is correct, then here is how you set it up in DLRS:
Parent Object = Account
Child Object = Account
Relationship Field = ParentId
Relationship Criteria = Account Status = 'Active' (make sure to use the API name of the field here)
Field to Aggregate = Id
Aggregate Operation = Count
Aggregate Result Field = # of Schools (this should be the API name of the number field you want DLRS to update)
Let me know if this works for you.
@@BluTigerAcademy Thank you for your prompt response. I diligently followed your instructions step by step, and I'm thrilled to report that everything is working perfectly now. Your guidance was incredibly helpful! 😀
Awesome!! Glad it's working!
@@BluTigerAcademy Many thanks for the guidance it is great for a new admin!!!!!
I have similar @DamianGotbete's scenario but with Campaigns instead.
I try to roll up a volunteer number for a child Campaign to parent campaign which itself is a rollup for a volunteer job.
I followed your suggestion and it works!!!
Parent Object : Campaign
Child Object : Campaign
Relationship Field : ParentId
Relationship Criteria : IsActive=true
Relationship Criteria Fields: IsActive
Field to Aggregate : GW_Volunteers__Number_of_Volunteers__c ---------> it is a Roll-Up Summary (SUM)
Aggregate Operation = Sum
Aggregate Result Field = Total Volunteer for parent campaign
However when I tried SUM the number of job done on the ALL child campaign it doesn't work.
Parent Object : Campaign
Child Object : Campaign
Relationship Field : ParentId
Relationship Criteria : IsActive=true
Relationship Criteria Fields: IsActive
Field to Aggregate : GW_Volunteers__Volunteer_Jobs__c ---------> it is a Roll-Up Summary (count)
Aggregate Operation :sum
Aggregate Result Field = Total Volunteer Job for parent campaign
Please could you advise?
Thanks
Error occured processing component dlrs__LookupRollupSummary2.Total_Number_of_Volunteer_Job_completed_PC. Value too long for field: fullName maximum length is:40 (FIELD_INTEGRITY_EXCEPTION).