Dan_Stevens_

Karina - can you explain how this would help in this situation?

Have a look now, Greg - does the idea now capture the full scope/capability?

In my example, this specific field is one that continuously toggles between true/false in CRM. Currently the value is TRUE. My use case in the idea above was to not do anything until the value changes back/resets to FALSE. If I understand what you're saying, we need to also take into account the ...

Hi Greg - I actually came across this and decided to create a new one that included a broader scope; and was more current (that one is from 2014). I agree - this would alleviate many of the race conditions we're experiencing today.

Is this relevant for both SFDC and MSD?

The first filter is will only include those with ParentCompany name when the second filter is applied. The second filter will not apply to any lead - just those with ParentCompany.If this still doesn't make sense, perhaps you can provide some real examples here.

Looks like the MS Dynamics one is still a work-in-progress: Default Microsoft Dynamics Field Mapping - Marketo Docs - Product Docs (not sure how long it has been in this state).

Hey Robb - every form on our site (Sitecore) is an embedded Marketo form. Have a look at the source code here, for example, to see if there's anything that might look different from your environment: Contact Us | Avanade. I can also get the specific embed code that's being used here (which you can...

Are you saying this isn't working for you - with these two filters?:ParentCompany is "xxx"BooleanField is TRUE