In cases where an administrator/programmer needs to mass update records, such as importing content for a new custom field or re-importing a single incorrectly mapped field from another source during a migration (without mass-delete and then re-import), Apex Data Loader should allow for a silent or stealth update mode which does not change the "LastModifiedByID" and "LastModifiedDate". It should be up to the administrative user whether or not they want the LastModified info to be destroyed by their update. Some workflows depend on knowing who last touched the record and when, and replacing it with an administrator/programmer ID just because they were doing something otherwise innocuous really screws everything up.
This could either be a keyword in the LastModified field(s) to signify "no update stamp" on a per-record basis, or a checkbox in the settings such as the "insert nulls" option, applicable on a per-batch basis.
2 Comments » Posted by tbsspm
Posted 11/17/08
Categories: Web Services API, Database Services, Force.com Platform