Do not want Workflow to update the Modified by date and user

(0) Share

Report

Posted on by Ben Markland

I have a workflow that updates a field on the lead form every time an activity is added. The problem is this workflow also updates the Modified on date and Modified by user. Is there a way to not overwrite these fields with the workflow or maybe have the workflow itself set the fields back? It seems the Modified on field is not editable in a workflow.

Thanks

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (2)

Mithilesh Kumar 10,047 on at

Like (0)

Report

Hi Ben,

Modified By and Modified On are fields which are updated by the system.

Like you said you are updating a field every time on Lead when you are adding an Activity.

This means you are modifying the Lead record, therefore the System is ought to update your Modified On and Modified By field.

Hope that make sense

Thanks

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Mithilesh,

I am also facing Problem with same Scenario.Is there any solution when a user has modified a record. modified by Field has to show the username?Not the system or Owner of the workflow.

Was this reply helpful? Yes No
Verified answer

mscrmba on at

Like (0)

Report

An answer to Kinnu's question:

Make sure it is a real-time workflow (Convert to real-time workflow) and execute as the current user. This will at least record who made the recent changes. But Modified on and Modified by are designed to always reflect the most recent changes made to the record.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (1)

Report

Hi Ben, Kinnu

As you are updating Lead record, system updating Modified on and Modified by fields.

"Modified On" Field update is correct and I don't think you can make system stop to update this field when entity record is updated. So I think there is no way here. In this case, I suggest you to create your custom Modified On field with different schema name and update it as per your need.

Regarding "Modified By" field, you can have little control on which User should show into this field, either user who created this workflow or the user under workflow runs.

I hope this help

Was this reply helpful? Yes No
Sayhaitokumar 7,042 on at

Like (0)

Report

Hi Ben Marklan,

i don't know why you need this scenario, Those two fields are updated by the systems, you can't make it stop. Because System want to track who are all made changes in the CRM environment and it will help the higher management for Auditing purpose

Was this reply helpful? Yes No
Suggested answer

mscrmba on at

Like (0)

Report

An answer to Ben's issue:

If you really need the original 'last modified on' and 'last modified by' information to be held on Lead then create 2 custom fields (a date field and a user lookup field) and then create a workflow/code that updates those fields when the Lead record is updated in a way that you want to know about (whichever fields/manual steps should give rise to the data being captured).

Was this reply helpful? Yes No
Toke 5 on at

Like (0)

Report

I have this same problem with the 'modified by' field. But in my case, the workflow has to be async (opposite to real-time workflow). So how to achive this, when the 'Execute as' setting is not an option?

Was this reply helpful? Yes No