nhabischWings

Got it, I figured as such that it wouldn't be able to be diagnosed but was curious if anyone had encountered similar issues. I will go back to our data team to double-check if there's any issues there.

@Darshil_Shah1 wrote:Well, you've come across a little quirk of how velocity processes boolean values. In short, the problem is that both "1" and "" (empty string) are processed as being a true value in Velocity. Try the below script: #set( $mktoBoolean = { "1" : true, "" : false } )#foreach ($item ...

Ah okay, so in the context of a Velocity script, there's no need to account for a NULL/empty state since it will only reflect a value of TRUE (actually true) or FALSE (actually false or NULL)?

Got it, that makes sense! I will look into that.Thank you again for all your help!

Hello,Thanks! In our case we have a daily update that data basically pulls from our core platform into Marketo via the API. So, in essence what would occur is that if someone opted out on a global level, we'd pull that down and (ideally) be able to note whom it was and then data run would both set t...

For what it's worth from someone also in the financial industry - here's what I do: 01) Send a single copy to my work email - the Compliance approved version02) Save that in a spreadsheet with the date of send, total sent and delivered, criteria for the list, any exclusions03) I also export lists of...