Forum Discussion
MikeTamoush
4 years agoQrew Commander
Yes, you are correct. The automation is the culprit. When an automation runs, it runs under the owners name (of the automation) which is yourself. Since the automation is modifying the record, boom, you are now the last modified by.
I am not sure if there is a way to actually update the 'Last Modified by' field, but you can capture the last modified by creating a new text field [Last Modified By Manual] (or something) and as part of the automation, set [Last Modified By Manual] to the [Last Modified By Field].
I believe since Last Modified By is an intrinsic field, you cannot overwrite it, but perhaps someone else will know otherwise.
------------------------------
Mike Tamoush
------------------------------
I am not sure if there is a way to actually update the 'Last Modified by' field, but you can capture the last modified by creating a new text field [Last Modified By Manual] (or something) and as part of the automation, set [Last Modified By Manual] to the [Last Modified By Field].
I believe since Last Modified By is an intrinsic field, you cannot overwrite it, but perhaps someone else will know otherwise.
------------------------------
Mike Tamoush
------------------------------
- MarkShnier__You4 years ago
Qrew Legend
Mike's answer is basically correct. You can have a formula User field called perhaps [Record last Modified by].
have the Automation write the [Last Modified by] field from the trigger record into a field called [Last Modified by of Trigger record].
Then have a formula field for [Record last Modified by]
IF(not IsNull([Last Modified by of Trigger record]), [Last Modified by of Trigger record], [Last Modified by])
That way the formula field will either have the last modified by of the trigger record or the actual made of last modified by if somebody went in and modified the record manually.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------