Skip to main content

Hi Guys,

I am taking over a new salesforce org which has financial services cloud in it. I am hearing complaints from the current team that every time salesforce release happens, they have to go to each permission set and manually run the security recalculate button to repopulate all the share records in each standard object. I feel this is a bit odd and will happen only if they use the standard permission sets which should be cloned for best practice. Do you guys have any best practices on how to manage the security recalculations on salesforce releases or deployments ? This takes a good amount of time and leads to large deployment times.

Buyan

8 respuestas
  1. 29 jul 2024, 3:20 p.m.

    @Buyan thyagarajand we do have several flows that are record-triggered, and even time-based, that will reassign records based on criteria. But even with that, if they are happening at runtime, there should be no recalculations required on release, only at run-time. The release would inherently have to change your record sharing in some way, to require it to re-run. What could be happening is at your apex level. If you are doing any manipulation with Apex, you should check that the apex is written in such a way that the sharing is not deleted upon a change in the records (by using sharing reasons). This is typically only impacting when a record share changes, but that may be something to look into as the share can be cleared upon resharing unless it is written into the apex to not do this. Again, I do not think a release would impact that, but if it's custom...it's possible.