Global Automation - Field Value Change Trigger

[Nikki Hylton]

Good afternoon,

We have an automation set up with the field value change trigger set to "value added", but it is also updating the field whenever a value changes as well. Any ideas?

Thanks,

Nikki

[Ash Yadav · Accepted solution]

Hi @Nikki Hylton , 

Can you post the rest of your automation rule if possible? 

Does the affected field allow for multiple values to be added? (i.e multiple components etc). 

Have you reviewed the audit log to see what event caused it to fire? 

I'll need the above information to be able to dig into it further :) 

Kind Regards, 

Ash 

[Nikki Hylton]

Hi Ash,

The full rule is pasted below. Essentially we have a custom field for "target end" that should populate with the value of "due date" when that field is initially populated (to preserve the initial target end date even when due date changes).  

Even though we have "value added" as the change type instead of "any changes to this field value", it is triggering when due date is initially populated AND changed.

Thanks for your help! 

Nikki

[Ash Yadav]

Hi Nikki, 

At a glance the rule appears to be fine so my next course of action would be to check if there are any other automation or workflow rules that could be causing the field to be updated on any value change. 

Do you have a snippet of the audit log of when this automation last fired? Might have some clues there. 

KR, 

Ash

[Nikki Hylton]

Hi @Ash Yadav  thank you for looking into this for us! 

We have another rule that updates the "due date" field that triggers this rule, but nothing else that updates the value on the "target end".

Here's a snippet of the audit log:

Thanks again,

Nikki

[Ash Yadav]

Hi Nikki, 

If I understand correctly, you want the automation rule only to fire when a value is added to the due date field but not changed correct? As in, the field should be empty and if it isn't, the rule shouldn't fire? 

If that's the case you could add a condition to check if the due date field is empty first. 

I'm not 100% sure that is what you're looking for but let me know. 

If you do need more help please show me the second automation rule and any associated workflows that could impact them so I can look into it further. 

Kind Regards, 

Ash 

[Nikki Hylton]

Hi @Ash

Thank you! That's exactly it, I tried adding the condition you suggested, and it's still triggering for edits.  However, I was able to use your direction and create an advanced compare condition, and that worked! 

Thanks so much for your help on this - truly appreciated!

Nikki

[Ash Yadav]

Hi @Nikki Hylton , 

You're most welcome! 

KR, 

Ash