How to handle list type data in transactional email | Community
Skip to main content
A
Anonymous
August 17, 2018
Question

How to handle list type data in transactional email

  • August 17, 2018
  • 1 reply
  • 2260 views

Hi all,

I have implemented Java client sending transactional emails including data from tokens sent in rest API call. So far everything has gone smoothly but now I faced a new challenge - I should include variable length lists to email from tokens sent in rest API call. Velocity script would be most the obvious solution, but can't find information if tokens sent in API call exists in Velocity context. Does anyone have information on this? Are there any other possible ways to include lists to emails?

Thx,

Janne

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

SanfordWhiteman
SanfordWhiteman
Level 10
August 17, 2018

Velocity tokens can't be sent as temporary tokens (along with the Schedule/Request Campaign APIs).

You have to update the token separately/permanently using the Asset API, then send the mail.

A
Anonymous
August 17, 2018

Sandford,

Thank you for your reply. That is what I was afraid of. Unfortunately updating tokens separately is no-go, the email is sent easily with thousands of different token sets in one "transaction" on client side.

SanfordWhiteman
SanfordWhiteman
Level 10
August 17, 2018

Why can't those key-value pairs (let's not call them "tokens," because they need not be individual tokens) be stored in only ​one ​Velocity token, storing a HashMap keyed on the Lead ID?

Terms & ConditionsAccessibility statement

Loading footer...