[SalesForce] How to Mass Update Records Without Changing the Last Modified By Field

I have a custom object that I need to do a mass update on to set a field on each to the same value.

I had written a snippet of code to execute in the Developer Console that would get all the correct records and update them. However, when testing users noticed all of them had the Last Modified By field set to my user.

It makes sense since I ran the code in the developer console. However, when pushing it to the production instance, they would like to not have the Last Modified By field set to my user so that the end users don't get confused.

Is there a way to do a mass update without having the Last Modified By be changed to my user? Or maybe reflect that the system changed it?

Best Answer

You can only do this upon inserting records. A script like what you're talking about will always modify the audit fields for Last Modified By and Last Modified Date. You'll want to vote on this idea.

Related Solutions

[SalesForce] Issue creating user and setting password

I had this same issue. What I did is add one more code to render the user id again.

User u = new User();
u.lastname= 'blabla';
u.ContactId = currentContact.Id;
u.email='blabla@blabla.com';
...
...
...
system.setPassword(u.Id, 'password123');

User uu =[select id from user where email='blabla@blabla.com'];

return uu.id;

[SalesForce] Does Upsert alway change the last modified date of the record

The last modified date of the every record will definitely change ,since an update of record will eventually happen even if field values are not changed .

If you need to explicitly code such scenarios ,i would definitely recommend to do an explicit update and update only those records whose field values have changed .

if(previous_value!=new-Value){
  //List for update
}else{
   //List for insert
}

Best Answer

Related Solutions

[SalesForce] Issue creating user and setting password

[SalesForce] Does Upsert alway change the last modified date of the record

Related Topic