Automation rule to exclude new entry from Change in a Custom field automation

A standard Automation rule for triggering an email when a Custom field value changes is triggered, even when the field is being filled for the first time. Ideally trigger should only be done when the field changes rather than first time update. Any solution?

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
8 commenti

Hi Hitesh Karkal,
maybe you can insert a filter where "Custom Field" is Not Empty.

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Hitesh Karkal! I can think of a way to do it when the field is filled for the first time, but depending on what type of field you have, you might have to build multiple automations to get it to respond how you want. What type of field is your custom field?

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Pietro Poli & Ali Moses Let me explain the situation.

1. Custom field "XYZ Date" is a Date type field.

2. I need a trigger when anyone changes the "XYZ Date" field which is working fine

3. However, I do not want a trigger when "XYZ Date" is being updated for the first time from blank to a date

4. I tried what you had suggested Pietro Poli i.e. adding a AND IF condition on "XYZ Date" = Non Empty, but wrike ignores the if condition, since it finds that the date is not blank now.

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

I suppose you could automatically set all XYZ Date fields for a specific date in the past instead of leaving them blank and then filter out that specific date. IDK, seems clunky though.

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Ali Moses This will not work since the custom field is  across multiple projects & the date varies from project to project & the trigger was to notice any change in the dates for a particular project. However, for a new project, when a PM updates the specific custom field, the trigger is raised as FIeld changed

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi Hitesh Karkal, I understand.

Two filters work in opposition.

You could try to do a double pass with two different Automations. But first create a custom field (Date Filled as Checkbox).

Automation NR 1:

- Trigger "XYZ Date" change
- Filter Date Filled = Empty
- Action: Date Filled = Checked

Automation NR 2:
- Trigger "XYZ Date" change
- Filter Date Filled = Checked
- Action: What you need to do

This way:
- At the first date change the only action is the checkbox that unlocks the second automation
- At the second date change you can make it do whatever you want

Make sense for you?

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Thanks Pietro Poli Just to clarify your solution, you are referring to creating a custom field with a checkbox option named Date filled correct?

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Automation rule to exclude new entry from Change in a Custom field automation
[this list is visible for admins and agents only]

Su
Didn’t find what you were looking for? Write new post