I'm a web, database, and network architect based in NYC, with specializations in the financial services, publishing, and SaaS sectors.
I build complex Marketo integrations for companies large and small... and can make Marketo forms and emails do things you never thought possible!
Check out my blog at https://blog.teknkl.com, which has Marketo-specific technical insights you won't see anywhere else, along with wider topics from my programming and systems work.
@JustinTy you can’t output the raw token like that, as I mentioned.
You must use the method in my post (output in <datalist>, read it from there, and URL-encode), because lead to...
Yeah, it’s for backward compatibility, but it does make sense.
We might expect HTML5, which requires UTF-8 encoding, would deprecate all named entities (they’d never be necessary ...
Of course. But you have to use the proper encoding, so don’t put the token directly into the href. Use the function from here to output into a <datalist> first and read it out:
<da...
There’s no better place than here. (And most of that is cross-posted to the official Products blog.) I’m really the only one in the world learning/writing at length about Velocity-...
You didn’t supply your full token code so I can’t show you where you introduced a syntax error.
Under “Person”, fields like Sales Owner Email Addressshould be easily accessible.
...
No need for any kind of "nesting". Those Person fields are all available in Velocity already. Just choose them from the tree.Also, you shouldn't be using ${var} (formal references)...