New answers tagged

1

When the owner changes, sharing calculations are performed sometime around the final commit, long after your triggers. This is what causes your shares to disappear despite your best efforts. You would need something like a future method or queueable to persist those changes correctly. That said, you might consider using Account Team Members, which tend to ...


0

What you're looking for are Big Objects. These are objects that have limited capabilities, but can store massive amounts of historical data. You could write triggers to copy the data from the object to big object on deletion or on a schedule. This way, you could delete the records normally and not have to worry about sharing, etc.


Top 50 recent answers are included