Bulk Edit Anomaly?

[miplatt]

Please see the attached log.

On Aug. 22, an attempt was made to do a bulk edit to copy a text field to a new notes field (per your previous suggestions). Following the edit, the records seem to have changed successfully.

Is the behavior depicted in the log healthy for this kind of operation? It looks like the system capacity was exceeded and perhaps it did not work completely.

In addition, we notice that ALL records now show Aug 22 as the date/time modified (other than the records created since then). Is there any way to reset the date/time so that we can see when the records were modified last before that? We need to track the modifications but for our purposes it is not desirable to have that time as the last modified time for all of the records. For example, if we need to know when a company was last contacted, we generally rely on that field of information. Can anything be done to rectify this?

[ZevToledano]

Regarding the error in the log, it looks like you had that while saving a bulk action, not while running one. My guess is that you selected too many filter values in the bulk action Filters - I see that this causes the error which we will fix for next version. In the meantime try to simplify the filters - there is almost never a need to select thousands of filter values. But since you say you managed to run it, I presume this isn't a problem anymore.

Regarding the 'modified date': This is a system field needed for many important things such as synchronization and conflict management. The system therefore sets it as needed (including while running bulk actions) and nobody is allowed to manually override it. If someone were to change the value, it could cause havoc with your data. Therefore, if you need anything except the real last modification date, then you must add a custom date field and use that instead.