Loading

'Last Modified Date' Changed for All Profiles When No Updates Have Been Made

Publiceringsdatum: Jun 17, 2026
Beskrivning
Symptoms:
 
  1. Almost all of the profiles in the organization indicate that they had been edited on a specific date when all administrators in the instance's company state that they have not made any changes to the profiles.
  2. When 'Setup Audit Trail' is checked, the only changes that are listed are the changes that have been made to the profile via Field-Level Security.
  3. The Field-Level Security was found to have been modified at the field level on the object, not the profile.

The above symptoms occur because a field has been created or Field-Level Security has been modified at the field level.
Lösning

The Last Modified Date on profiles changes automatically when a field is created or when Field-Level Security (FLS) is modified at the field level on an object. This is expected Salesforce behavior, the Setup Audit Trail will only reflect profiles where values actually changed.


Notes:

  • The 'Setup Audit Trail' will only show the profiles that have actually had values change or stating that a field has been created and no profiles display as changed.
  • This article refers to the 'Last Modified Date' field and not 'Last Modified By'.


Last Modified Date' changed for all profiles when no updates have been made:

Step 1:
Run a Debug Log to check if there is a trigger on the affected object that may be causing profile modifications

Step 2:
Confirm to the user if he or she created a process or rule to cause the trigger for this to deactivate.

Step 3:
Go to Setup, then Quick Find type Deployment Status

Step 3.1
On Deployment Status then Succeeded select view details of the record that displays successes check the Validated then compare to affected record last modified date if the value is the same then refer to a person at Deployed By

Knowledge-artikelnummer

000386124

 
Laddar
Salesforce Help | Article