Faster Account Sharing Recalculation in Salesforce

[@ATinAction]

I love this series! There are so many times when I wonder, "what exactly is going on behind the scenes to make this happen?" Thanks for bringing in the product people who can help us understand. 😃

[@ATinAction]

... ps, I have questions like this every once in a while- how exactly does this work? what is happening in the background? What's the best way to submit questions, to see if it's interesting enough for others to create a post or video?

[@SalesforceArchitects]

Please drop them in the comments here!

[@SalesforceArchitects]

Glad you enjoy it!

[@sun10647]

Thank you for the presentation. you touched briefly about performance. Looking for additional clarity as in, in an org with a bit of lookup and ownership skew, will this feature impact on page load performance for list views, SOQL query performance, reports, etc. now that bringing all of these on contacts, cases and opportunity(eventually) will need to join on Account share table. Traditionally, what we were led to believe is these additional shares were persisted to facilitate rapid scanning and minimize the joins necessary to determine record access at run time. With this will that slow down as an inevitable side effect, I guess is the question.

[@SalesforceArchitects]

Great question. Here's the feedback we received from the Product Manager: "Faster Account Sharing Recalculations are for various changes (Account owner, sharing rule, Account owner Role, …). The end-user experience will not be noticeably worse and could be significantly better depending on the configuration and data. However, that isn’t the goal of this specific feature. We aren’t trying to elaborate every single scenario where you may get faster end-user performance either."

[@arangari]

@@SalesforceArchitects what about the CPU time consumption? is the CPU time taken before and after activating the feature is computed against transaction's limit or outside transaction's limit? are there significant difference between earlier behavior.

[@dieffrei]

How can I check those jobs using API? E.g when you deploy permission sets they recalculate all related permission set groups it could fail upcoming deployments, what can be done is retrieving permissions set groups status. My question: How could I check OWD change jobs status?

[@SalesforceArchitects]

Great question! See this link: help.salesforce.com/s/articleView?id=sf.monitoring_background_jobs.htm&type=5

[@deepthitangudu3886]

Hi, can you please share any of the sample custom logic or soql query in order to find the child implicit cases or contacts using accountshare to get the result count after enabling faster account sharing calculation

[@SalesforceArchitects]

You will see the entry "ImplicitChild" in the RowCase on a share table (for example OpportunityShare or AccountShare). No special SOQL needed.

[@koraysahin7924]

@SalesforceArchitects will this update affect the way how I set up sharing rules, rules, territories etc. regarding the access of cases, contacts and opps?

[@SalesforceArchitects]

Hello! This will not change how you setup record access based, it will just speed up the calcs themselves. THis is still your go to guide for designing record access for scale: resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/draes.pdf

[@GouravBhalla-b4u]

If our Apex code doesn't utilize 'rowCause' anywhere, will this release update have any impact on our system?

[@SalesforceArchitects]

Regardless, you could still benefit from faster Account Sharing Recalculations. Test it out in a sandbox of course!