michaelstancil

@Jo_Pitts1 gotcha, let me take a look! @SanfordWhiteman (and Jo) if it WAS possible, would the revised code be correct at least?

@SanfordWhiteman Thanks for the pointers, you made me realize I needed another value to key off of. #set( $lead.CustomObjectEmail = "CATCHALL@EMAIL.COM" )#foreach( $Opportunity in $OpportunityList )#if( $Opportunity.VARIABLETOUPDATEAGAINST.isNotEmpty ) #set( $lead.CustomObjectEmail = $Opportunity....

Welcome to my world haha. So we have Account and Sales owners, but because of how our system works they may get moved off to a variety of reasons and replaced with a catchall. Should that opportunity update to be valid again, the catch-all will remain on the account/sales level, but the in-opportuni...

That's exactly what I was hoping...as I was going to use that new field and perform a change data value. Are there any other ways around something like this?

@SanfordWhiteman Got it on the operators vs. output!Then you would never expect Velocity to see the objects! Sometimes (i.e. 2nd-level+ objects) a Smart List filter can see objects but Velocity can’t. But never the other way around.If the person is a Lead, and the CO is only available via the Contac...

@Jo_Pitts1 Oops! Thanks for catching!

@Jo_Pitts1 @SanfordWhiteman The object is the correct one, and I've verified it does have data within SF, as well as Marketo, as I can see the values in each specific field when I apply the object as a list condition. Additionally, I am selecting all of the fields within the custom object when I'm i...

@SanfordWhiteman The result in the email is: ${AVM_Values__cList} pineapple

@Jo_Pitts1 @SanfordWhiteman So I asked our engineering team for some assistance, and we did some debugging. We're able to go into the Opportunity Loop, but when we loop through the AVM, nothing happens. So in the code below, we get pineapple, but not oranges. Is there something basic I'm missing? ...