Phillip_Wild

A lot of good thoughts here!I went through a similar process myself around 6 months ago. We have been with Marketo for about 3 years. I framed it to the other vendors as this: What's your big killer feature that Marketo doesn't have that will justify the 6 months - 1 year that we will spend rebuildi...

Respectfully, I think most people would be super annoyed at your brand for tricking them with a fake forward. I've heard many people complain about the same strategy with using "Re:" in a subject line which clearly isn't a reply. It's deceitful and you will instantly erode any trust your subscribers...

Thanks so much Sanford! That has done the trick. I previously thought I had tested that - but I'm guessing I used ${variable}[0] instead of ${variable[0]} . With the proper notation, this works just fine.Your trick to show syntax is very useful too, thank you!

Hi SanfordSorry, I'm not exactly sure what you mean. Do you mean highlighting the code vs the comments? If there's a better way to display this let me know - it doesn't make it easy on the eyes!

Thanks everyone, it seems to be working correctly now!Once I removed the brackets and referenced a specific part of the array it is working fine!

Thanks Sanford. Unfortunately I'm still having trouble - and I don't think it's related explicitly to that .split functionality now. When I use:#set ($DossierArray = ${lead.wishListtoWin2016Dossiers}.split("\u002f"))$DossierArrayI'm still getting that same lexical error above. Even when I replace th...

Thanks Sanford.I'm playing around with it and unfortunately having some trouble. I understand I need to escape the special character "/" in order to split the string based on that - but I can't seem to even get a basic split working.Here's my code: #set ($DossierArray = ${lead.wishListtoWin2016Dossi...