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
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
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!
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,
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,
It looks like you're new here. Sign in or register to get started.
