SanfordWhiteman

@JustinTy you can’t output the raw token like that, as I mentioned. You must use the method in my post (output in

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 if you really have the ability to encode any BMP character directly). But the reality is people still save things using I...

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

@Chandana_kavuri please return to your thread and check responses.

@tomh2 please return to your thread and check responses.

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-in-Marketo specifically. The link you posted to Velocity 1.7 uses the same syntax as Marketo (and that’s the right versi...

You still need quotes around string literals like "Base".

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 Address should be easily accessible.

Sent Email activities are only stored for 90 days. So it's not possible to create such a report.

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) here, just $var (simple refs). And don't use ==, use .equals().