Help with velocity script

Question

Hello all,as the title says, I need help with a velocity script I'm planning to use on a campaign to be sent out in the next days. Let me start by saying that I am not a developer, so the extent of my ability with Velocity is quite limited...The velocity script simply shows a list of names and dates in a table-like format, but I've come across a couple of obstacles:1. the date format seems to be the "american" one (mm-dd-yyyy), however it would be best if it showed in the "european" format (dd-mm-yyyy). A workaround I found to avoid adding more code to the script is to have the "Date" field on the custom object as a string instead of a date, but I fear that doing so might hinder or limit some features related to smart campaign operators.2. this is the most important: is there a way to limit the number of records appearing on the email to just those that are added each time? For example, if I use the "Added to custom object" trigger to send an email to a lead that already has 4 records in his custom object, adding 2 new records to it, my goal would be for the email to show only the 2 new records added, but it instead shows all 6 records.This is the code (very simple) that I am using: #foreach ($CustomObject_c in $CustomObject_cList) #end

Name		End date
${CustomObject_c.lastName} ${CustomObject_c.name}		${CustomObject_cList.endDate}

What can I do?Thanks,Francesco

SanfordWhiteman · Accepted Answer

What I meant was that I essentially intend to make each upload twice, once for the actual upload of records and a second time for the update of the boolean field. I'm aware of the race condition, but these actions don't necessarily need to be made in real time so it's possible to have a "Wait" step in there to handle the race.

Also, I know this might not be the best approach but until the sync with SFDC is done my options are limited... Consider that we will have roughly one upload a month, so we have plenty of time to add wait steps that can manage the race.

In my mind, the campaign could look something like this:

Trigger - Added to Custom Object

Filter - Member of list (this is to help narrow down the leads to exactly the ones we need)

Flow

Wait 1 day
Send email with Velocity script
Send alert to tokenized email addresses (hence the need of a trigger smart campaign)

Schedule - Each lead can run through the campaign every 2 weeks or so (this is to give a buffer time where we can re-upload the file to update the boolean without triggering the SC a second time)

Does this make sense?

Can't solve race conditions with a wait step (and this one is related to the SFDC sync interval). Tons of Marketo integrations are broken because people didn't think about synchronization and concurrency. But let's leave that aside for now.

Given the broad interval between uploads and the other assumptions you're making, I think you're actually overengineering your design. Why not just tag the COs with a timestamp and only process the ones from the previous day? After all, your second upload to flip the bit is assuming they're done without doing any further checking.

SanfordWhiteman · Answer

For the date formatting, check my notes here and here.

For getting just the latest record (singular) that triggered the SC each time, you should use the ${TriggerObject} instead of looping over the list.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded