VTL Token | Malfunctioning?
Hi all,
I open this thread to report a malfunction (or so it seems), of a velocity token.
Before I explain the malfunction though, it is necessary to put the problem in context.
Due to the integration with CRM (D365), I have a token that is written via API.
Within this token are multiple links.
All the links have this composition: (www.[...]_Registration.html).
I would like to parameterize these links with the GUID of each user's Company.
However, obviously, it is not possible to have "nested tokens," so to act on a link that comes from CRM and is already contained in tokens, another way is needed.
So we thought of writing a VLC Token that, thanks to the "Program Member Data," does a replace of all the final parts of the links, like this:

## GET EVENT DATA FROM MEMBER FIELD
#set($event_invitation_token = "" )
#if($member.eventInvitationToken && !$member.eventInvitationToken.isEmpty())
#set( $event_invitation_token = ${member.eventInvitationToken})
#end
#set($event_invitation_token_edited = $event_invitation_token.replace("Registration.html","Registration.html?aid=${lead.accountid_account}"))
$event_invitation_token_edited
This is the VLC token in its entirety.
The action involved is given by "replace."
So. what happens?
Hapens that the operation of the token is random, and different for each user.
In fact, it seems that the vlc token cannot act on the entire contents of the original token, but processes about half of it--a little more, a little less.
What do you think could be the causes?
Base Token (see the 4 block with button)

VLC Token for user A (just 2 block "processed" by the token):

VLC Token for user B:

As you can see, 2 blocks processed, started to process the 3rd one, than stopped.
Really curious to read something!
Thank you to anyone who wants to take a few minutes to try to understand the problem!