Create a Roll-Up Summary Field with Salesforce Flow

Рет қаралды 5,780

Жыл бұрын

⭐️ Want to use Salesforce Flow to automate your business? Join our 2-day live class next week! Use coupon code “KZfaqSUB15” to save 15%. www.rotive.io/live-flow-training
Learn how to create a roll-up summary field using Salesforce Flow in our Automation of the Week! 📺 What are Roll-Up Summary Fields: • What are Roll-Up Summa...
▶️ SUBSCRIBE TO OUR KZfaq CHANNEL: go.rotive.io/youtube
🤖 LIVE SALESFORCE FLOW CLASSES: go.rotive.io/live-salesforce-...
⚡️ SALESFORCE COURSES:
→ The Salesforce Reporting Crash Course for Beginners: go.rotive.io/reportingcourse
→ The Pardot (MCAE) Course for Beginners: go.rotive.io/pardotcourse
→ DIY Pardot (MCAE) Implementation Course: go.rotive.io/diypardotimpleme...
→ FREE The Salesforce Validation Rules Crash Course for Beginners: go.rotive.io/validation-rules...
🍎 VIEW ALL COURSES AT ROTIVE ACADEMY: go.rotive.io/academy
-------------------------------------------------------
Rotive is an official Salesforce Partner that helps small businesses automate their processes.
📍 Visit our website: go.rotive.io/homepage
👍 Follow us on LinkedIn: go.rotive.io/LI

Пікірлер: 37

@michalmacak 5 ай бұрын

Hey Brian, how about the assignment with operator Equals Count instead of loop?

@Rotive 4 ай бұрын

Hey Michal, that is a great option and more efficient than a loop! If all you want to do is count the the number of records in the collection, I think using that assignment step instead of a loop is the way to go. Thanks for bringing it up!

@Rand_om123 11 күн бұрын

Please note, using count instead of loop will NOT work for the delete flow.

@mrsess5932 6 күн бұрын

Thank you so much! This was really helpful

@stevenoffutt697 4 ай бұрын

I tried many other videos and kept getting stuck. Your video helped me figure it all out. Thank you so much.

@Rotive Ай бұрын

Glad it helped! We appreciate the comment!

@Arckham77 3 ай бұрын

Awesome video, Brian! Thank you so much. It helped me a lot

@Rotive 2 ай бұрын

You're welcome! Thank you for the comment!

@user-se4po9tc4m 7 ай бұрын

I follow the steps in other scenario and works perfect!! Thanks!

@Rotive 4 ай бұрын

Glad it helped. Thanks for watching!

@AnnaSzabo Жыл бұрын

What a helpful video! Watching now, thanks, Brian.

@duishonabdykerimov2828 8 ай бұрын

Awesome Brian👍💥

@Rotive 7 ай бұрын

Glad you enjoyed it

@balamuruganp9017 Ай бұрын

Hi @brian can you confirm is it possible include both creation and reparenting in one flow...

@Rotive Ай бұрын

I don't see why not. You can create a record and at the time of creation select a different Parent/Lookup value. Make sure the field in question isn't a Master-Detail field with the reparenting option turned off. You might run into some trouble with that.

@user-ep6sx8tr2t 14 күн бұрын

I tried in a sandbox an works. I just copy from the sandbox to the real environment and do nothing. I don't get it

@VandennKrouch Жыл бұрын

I followed this tutorial and applied it to my unique situation and it worked perfectly...mostly. I have a Sales Transaction (Parent) and Checkout Items related list (child). I could not use the Roll-up Summary field type because of some limitation and so explored whether Flows could do the trick. You showed me that it could! Thanks. So, when I add new Checkout Items or modified an existing Checkout Item, the Total Cost field in Sales Transaction works perfectly. However, when I delete a Checkout Item, nothing happens. The information from the deleted Checkout Item (subtotal) still exist in the Total Cost and it still exist in my Created HTML table of Checkout Items (also your tutorial). I've tried a few things on my own but still can't get a deleted action to update the Total Cost in Sales Transaction. What do you suggest? Thanks.

@Rotive 11 ай бұрын

You'll want to create another Flow to trigger off of deletion. You can do this with a record triggered flow. So you'll have one flow when a line item is edited or updated and another one that runs when an item is deleted. It does make it a bit more complicated.

@user-ju9ly1zq2f Жыл бұрын

Great video! Question... Instead of counting the number of contacts within the account I would like to count the number of retail locations (sub parent) based on the retail group (parent) account. Do I just need to place the retail type id (retail group) under the filter account record of the flow? Or what alternative can I do?

@Rotive Жыл бұрын

Hey Bryan, it's hard for me to be specific since I don't know your Org, but it sounds like you're on the right track: Get All Accounts with Parent ID = to RecordId(the account you,re on). If there are other accounts with that same parent that aren't retail locations, then you would need to add in that filter to exclude non retail accounts.

@scottthompson8919 7 ай бұрын

Any suggestions for when you aren't counting the number of records but summing a field on the record with decimals? I found the create and update flows work well, but the delete results in the summary field being off by -1 rather than the actual amount.

@BrettShorts 4 ай бұрын

I'm also looking for this...

@EMek-tq6wc 5 ай бұрын

Is it possible to built roll up summary for self lookup relationship? My object has hierarchy by looking up to Parent on the same object. I wanted to roll up how many children under the parent. Is it better to use code instead of flow? Any suggestions ?

@Rotive 4 ай бұрын

This is a tough one for Flow because we don't know how far the hierarchy goes. It could be two levels or twenty, etc. You'll have to build in the logic to keep getting records at each level to see if they exist and do that for as many levels as you think could be present.

@user-xs8mp6iy4j Жыл бұрын

@Brian - Have you tried uploading 200 contacts and see if the Flow is working? Its giving me an error "You or your organization has exceeded the maximum limit for this feature", Any idea?

@Rotive 11 ай бұрын

Hey there, I'm not sure which feature they're talking about. Do you still get this error if you mark the flow as inactive? I don't think it's related to the automation.

@ArunKumar-9945 5 ай бұрын

Hii Brian Excellent Class i had seen on flows topic i have a doubt in update scenerio why we use 2 subflows ?

@Rotive Ай бұрын

It's needed because the triggers are different. If you want to take an action when something is created, updated, or deleted, you need two flows, because created and updated can be done together. Deleted is its own trigger.

@jaimevalls6194 Жыл бұрын

Great Stuff Brian! Can you use this information to make a report on how many contacts were created by month? I want to do something similar by calculating the number of events made in each account and compare it with the pipeline in any given month an see the ratio of Events:Opportunities

@Rotive Жыл бұрын

Hey Jaime, I would actually just use reporting to accomplish this. It's difficult to use roll up summaries to show you data over time. That would require you to a roll up summary fields for each time frame. Instead you could try using a Joined report to show you Opportunity and Contact data by the shared account. I think that would help you get the info you're looking for. I just reread your comment. If you mean contacts in terms of activities, I would still recommend trying the reporting option first to see if that works.

@jaimevalls6194 Жыл бұрын

@@Rotive Hey thank you for the info! I will look at it

@peyton3419 7 ай бұрын

Built something similar and found that deleted > restored Contacts don’t trigger the Flow unfortunately

@Rotive 7 ай бұрын

That's a good insight. Thank you!

@krollo Жыл бұрын

homerun on the subflow concept!

@Rotive Жыл бұрын

Thanks! Glad you liked it, Andy.

@terrycole Жыл бұрын

For what it’s worth, you could do an assignment and count the collection instead of looping. And if one changed from null to an account on a contact, this might fail. No matter what, I would probably put one decision in your lowest Subflow to quit if the account ID is not valid. Enjoy and recommebd your tutorials. You have a brevity that I do not. Lol!

@Rotive Жыл бұрын

@@terrycole Hey Terry. You are absolutely right! I didn't even realize that. If you're just counting the records using the assignment step will save you from the loop. Thanks for that. I think your addition of a decision to confirm the account ID is valid is another good improvement. Thanks for the comment!