Salesforce Fact #975 | Field history tracking issue with system context

There's a loophole with the field history tracking when the automation is executed in system context.

If the user doesn't have the object access/field access and the automation executes in system context without sharing mode, then the record gets created and the audit fields are stamped correctly but the field history related list stays blank.

Here's the relevant Idea link: https://ideas.salesforce.com/s/idea/a0BHp000019OmswMAC/enable-field-history-for-system-mode-dmls-regardless-of-object-permissions

Reference: https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000mjpO60AI

Comments

Post a Comment

Popular posts from this blog

Salesforce Fact #913 | Access selected record field values in screen flow lookup w/o Get Records

Image
Suppose we are using the Lookup element in the screen flow and once a record is selected, we would like to get the value from other fields. Now, Lookup provides record Id and record Name field values by default. So in order to get the other field value we need to use a Get Records. But hold on! There is an option to get the field values without using a Get Records element. We need to define a child sobject variable and then in the advanced section, set the parent field Id with the record Id of the selected record in Lookup. In this example, we have a lookup of Account record and we are using a Contact record variable and setting the AccountId field with the selected record Id and later on accessing the field values from account. Attached are the screenshots.
Read more