Loading

Difference between SystemModStamp and LastModifiedDate

Udgivelsesdato: Jul 18, 2024
Beskrivelse

You may notice that some records have a different 'SystemModStamp' and 'LastModifiedDate.'
Løsning


'LastModifiedDate' and 'SystemModstamp' comparison


'LastModifiedDate' is the date and time when a record was last modified by a User, and 'SystemModstamp' is the date and time when a record was last modified by a User or by an automated process (such as a trigger.) In this context, 'trigger' refers to Salesforce code that runs to implement standard functionality, rather than an 'Apex trigger.'

As a result, 'LastModifiedDate' and 'SystemModstamp' will differ when automated processes update the records, which will happen in the following scenarios.
  • The archive date is extended by more than 365 days.
  • An existing picklist value is updated and not replaced with an existing picklist value.
  • A Contact's e-mail address is flagged, as per the 'Email Bounce Management' configuration.
  • The 'LastActivityDate' field is modified.
  • A Roll-up summary field is created, which will update all the parent records' 'SystemModstamp' asynchronously. Note: Recalculation will also take place if the 'Summary Type' is updated.
  • Some Salesforce internal backend processes will also update 'SystemModstamp,' as 'SystemModstamp' is used internally to signal that a record, or related data, may have changed - and that internal processes may need to synchronize themselves to the new record data. 

Note. This can happen asynchronously in some cases.

For more information on how an SOQL query's performance can be impacted by the use of each field, refer to Force.com SOQL Performance Tips: LastModifiedDate vs SystemModStamp.
Vidensartikelnummer

000387261

 
Indlæser
Salesforce Help | Article