Workflow not working on field change

(0) Share

Report

Posted on by Ciaran Reynolds

230

I have a workflow which should be triggered on the opportunities entity whenever a custom field is changed. I have ticked the 'Record field change' box and selected the custom field. When I go on to a record and amend the custom field referenced in the workflow nothing happens. Why would this be? I have even tried changing the workflow to run when several fields change (including out of the box fields) but still nothing happens.

*This post is locked for comments

I have the same question (0)

All responses (16)

Answers (1)

gdas 50,091 Moderator on at

Like (0)

Report

Hello Ciaran,

Are you expecting at the time of field change the workflow will be fire ?

It is not, you need to save the records to get workflow fired , workflow does not work in client side changes until you save the record .

Was this reply helpful? Yes No
Aric Levin - MVP 30,190 Moderator on at

Like (0)

Report

Is this Real Time workflow or Async workflow?

Are you saving the record as Goutam answered?

Was this reply helpful? Yes No
Ciaran Reynolds 230 on at

Like (0)

Report

I know the workflow will only begin when the record is saved. I should have mentioned in my question that the workflow is not working when I change the custom field and then save the record. I have checked the process sessions and nothing ever appears. If i set the workflow to 'On demand' then I can manually add records to the workflow and it works.

Was this reply helpful? Yes No
Ciaran Reynolds 230 on at

Like (0)

Report

I have tried both real time and async but still nothing happens

Was this reply helpful? Yes No
Justinjose 2,707 on at

Like (0)

Report

Hi Ciaran Reynolds,

Can you look into the workflow scope and make sure it is set to Organization. The workflow will run on records owned by any user in CRM. Since it will trigger for all records, organization scope is the most used scope option.

1. User

Choosing this scope means the workflow will run only on the records owned by the same user as the workflow user.

2. Business Unit

This means the workflow will run on all records owned by the users of the same business unit as the workflow user.

3. Parent: Child Business Unit

With this, the workflow will run on the records owned by the users of the same business unit as the workflow user as well as any child business units.

4. Organization

The workflow will run on records owned by any user in CRM. Since it will trigger for all records, organization scope is the most used scope option.

Thanks

Justin Jose

Was this reply helpful? Yes No
Ciaran Reynolds 230 on at

Like (0)

Report

Hi Justin,

The scope is set to organisation. I even tried changing the scope to user as the record I'm running tests on is owned by me.

Was this reply helpful? Yes No
Shidin Haridas 3,499 on at

Like (0)

Report

Hi Ciaran,

Possible to share the workflow details here?

If not, try to create a new workflow and see if you are facing the same issue with the new workflow as well.

Was this reply helpful? Yes No
Ciaran Reynolds 230 on at

Like (0)

Report

Hi Shidin,

I have tried recreating the workflow but I am faced with the same issue. You can see my workflow below.

Here is a screenshot of my workflow in draft. Please note that for this instance we have renamed opportunities to properties.

Below you can see the field I want to trigger the workflow, when changed and saved.

Below you can see the same field on the form (circled in blue), which I am changing then saving the record but the above workflow does not even begin.

Was this reply helpful? Yes No
Verified answer

Shidin Haridas 3,499 on at

Like (1)

Report

Ciaran,

All looks good on the workflow's end.

So, you mean to say that the workflow is working fine when you process it 'On Demand' (through Run Workflow), but not working from otherwise, even is real time or async workflow?

Even if the Async process were to be down (highly unlikely for Online), the real time should still kick into place and work.

Just for debugging purpose, can you add a 'Conditional Branch' and say 'Create a new Account record' or something?

And then, try again as real time and background workflow?

PS: Silly tip, but i hope that the workflows were activated and published.

Was this reply helpful? Yes No
Ciaran Reynolds 230 on at

Like (1)

Report

Yes that's right.

Tried with the unconditional branch and it's now working! How strange... Thanks a lot for your help Shidin.

Was this reply helpful? Yes No