My Zap filter in the last step is not working right. Filter in my last step is set so that : Opportuntiy Stage Name exactly match “Pledged”, Membership Start Date = does not exist, and Membership End Date = does not exist. Screenshot of the filter rule below.
However i attached a sreenshot with the zap run history and the Salesforce opportunity side by side. In the opportunity, Stage = closed won, and Start Date and End Date exist.
Could I please get some help to review this, because this filter error is happening for the second time.
– Asia Society Australia
Best answer by christina.dBest answer by christina.d
Hey friends, I wanted to swing by and summarize some of the recommendations here! 🤗
GetUWired wrote:
Hi @ASAoperations
I believe Zapier caches data from Salesforce in that trigger…. I have experienced similar issues before. The work around i used was to look at the id from the trigger step it should be something like {object_id}-{stage_name}. This value was always correct where as the stage value was occasionally an old value which looks like what you are experiencing here.
The steps for the workaround would likely be: Action- Delay
Action - “Look for Opportunity”
Action - Filter
Keep us posted how this works out for you, @ASAoperations!
It’s likely because you added wrong custom fields to the filter. Check if there are other start date / end date custom fields available in the trigger step.
It’s likely because you added wrong custom fields to the filter. Check if there are other start date / end date custom fields available in the trigger step.
Hello,
Thanks for your reply.
There’re no other custom fields. Plus the field ‘Stage’ = Closed Won shouldn’t have passed the filter.
Are you able to locate those fields being returned in the DATA OUT from the Zap trigger step for the Zap Run related to the record in question?
Please post a screenshot of that for us to have context.
Hi Troy,
here’s the screenshot of the data out in the trigger step.
however as I mentioned, the filter where the issue happended in before the last step of sending an outbound email. Before this filter is a DELAY step. During this delay, the opportunity had been closed as CLOSED WON because the invoice had been paid, and hence those fields have been updated. The filter should check the opportunity again for these fields.
I believe Zapier caches data from Salesforce in that trigger…. I have experienced similar issues before. The work around i used was to look at the id from the trigger step it should be something like {object_id}-{stage_name}. This value was always correct where as the stage value was occasionally an old value which looks like what you are experiencing here.
I believe Zapier caches data from Salesforce in that trigger…. I have experienced similar issues before. The work around i used was to look at the id from the trigger step it should be something like {object_id}-{stage_name}. This value was always correct where as the stage value was occasionally an old value which looks like what you are experiencing here.
Hello,
That’s really helpful. So with the workaround, should I add a ‘Look for opportunity’ step after the Delay step and before the Filter step?
Hey friends, I wanted to swing by and summarize some of the recommendations here! 🤗
GetUWired wrote:
Hi @ASAoperations
I believe Zapier caches data from Salesforce in that trigger…. I have experienced similar issues before. The work around i used was to look at the id from the trigger step it should be something like {object_id}-{stage_name}. This value was always correct where as the stage value was occasionally an old value which looks like what you are experiencing here.
The steps for the workaround would likely be: Action- Delay
Action - “Look for Opportunity”
Action - Filter
Keep us posted how this works out for you, @ASAoperations!
