Conditional checks based on custom deal fields not working

Ask a question
1

Hello all,

I’m at the very end of development and hit a snag, one that someone may have run into.

I have 3 pipelines:
pipeline 1
pipeline 2
pipeline 3

in each pipeline I have 1 stage
pipeline 1/stage 1
pipeline 2/stage 1
pipeline 3/stage 1

We have custom deal fields created and automations for each pipeline/stage that does the proper math depending on which deal you have.

Each pipeline/stage/automation combo works on their own, however a customer can have a deal in each stage, and this is where things go wibbly/wonky.

John Smith has the following created:

pipeline 1/stage 1 = DEAL p1s1 – created 1pm
pipeline 3/stage 1 = DEAL p3s1 – created 2pm
pipeline 2/stage 1 = DEAL p2s1 – created 3pm

I have an automation triggered at a specific time to run for pipeline 3/stage 1 Deals, and within that automation I have the following IF/ELSE:

IF
HAS DEAL IN STAGE pipeline 3 stage 1
AND
custom deal field 1 greater than 0

One would assume that this would look at custom deal field 1 within “pipeline 3/stage 1”, however, this logic does get the HAS DEAL IN STAGE part correct, but when looking at custom deal field 1, it looks at the value in the last created deal, in this case that deal is : “pipeline 2/stage 1 = DEAL p2s1 – created 3pm”. Not desired…

This acts the same with with a WAIT

WAIT
HAS DEAL IN STAGE pipeline 3 stage 1
AND
custom deal field 1 greater than 0

I am looking for the behavior to set the pipeline/stage/deal within the automation so IF/ELSE and WAITs work on the proper custom deal field, similar to how the math operations work where we can specify the pipeline.

Has anyone else run into this? Does the above make sense?

I sent an email to help@ and am waiting for a response, so thought I would check here.

thanx for any help.

–kev

1 Like
2

I found this page:

which talks about triggered deals. All I see in the WAIT and IF/ELSE is “Has deal in” not “Triggered deal”. What needs to take place to get the “This deal is in stage” options?

thanx!

–kev

1 Like
3

does anyone have any workarounds to this? our automations are based off doing conditional checks and WAIT’s on custom deal fields.

It’s disappointing that this is not a feature.

does anyone know if zapier would help in this scenario?

any info or direction to take is most appreciated.

Happy holidays to the states!

thanx

–kev

4

Curious if anyone had a Zapier workaround?

I’m in a somewhat similar scenario. Each deal that enters the automation will be treated for that particular deal only. If a contact has a second deal that enters the automation, logic should treat that particular deal. All logic within the automation is linked to custom deal fields. However, I realized while the logic looks at my custom deal, it does not isolate the logic to the triggered deal and instead looks at all deals for that contact. Therefore personal tokens were piping in information linked to another deal as opposed to the triggered deal.

AC support confirmed this “you can’t force an automation to look for deal fields specific to one deal. if you have more than one deal in the same pipeline, there’s really no way around it”.

Thanks!
Jess

5

@zicasso,

I have not found a workaround for this, I even tried multiple pipelines, and that still didn’t work as AC looked at ALL deals. We are looking to expand, however, do to this limitation in AC, we cannot even rollout what we need.

Would love a way to do a conditional check on a custom deal field for a specific deal. If that one addition got implemented, HOLY COW would some cool stuff be able to be done.

Please AC dev team, give us the ability to do conditional checks (and math operations) on custom deal fields for a specific deal.

1 Like
6

It seems as though we now have the ability to set our logic to “this deal”. See article:

1 Like