SOLVED

Looping condition sorting for bulk data in Custom Objects

Go to solution
Highlighted
Level 2

Looping condition sorting for bulk data in Custom Objects

In a loop condition, for each item business need is to sort it twice. 

#foreach( $myList_c in $sorter.sort($myList_cList, "date:desc") )
#set( $mySortedList = $sorter.sort( $myList, ["field1"] ) )

 Considering, more than 1 millions data sets, will this behavior result into

1. email delivery to be delay more

2. soft bounces and campaign response result affected

 

Tags (2)
1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Level 10 - Community Moderator

Re: Looping condition sorting for bulk data in Custom Objects


Considering, more than 1 millions data sets, will this behavior result into

1. email delivery to be delay more

2. soft bounces and campaign response result affected


I would have no concerns about sorting a list of < 100 items twice, rather than once, in a single email assembly. The overhead is infinitesimal.

 

However, sending 1,000,000 emails at once is a decision not to be taken lightly, regardless of what Velocity functions you call. Be prepared to be throttled and/or to have a high bounce rate, nothing to do with VTL.

View solution in original post

2 REPLIES 2

Re: Looping condition sorting for bulk data in Custom Objects

If you use a lot high end velocity scripting for lead involve Custom Objects and their properties into the script and perform sorting and filtering math operations. Those high-end features can add latency in email delivery as more processing has to be done these delays can range from milliseconds to even a few seconds, also the size your smart list for email send will also affect the processing time. Also regarding soft bounces, I believe a correct working scripting does not cause a soft bounce however a Velocity token parsing error does results in a Soft Bounce. 

Best,
Darshil
Highlighted
Level 10 - Community Moderator

Re: Looping condition sorting for bulk data in Custom Objects


Considering, more than 1 millions data sets, will this behavior result into

1. email delivery to be delay more

2. soft bounces and campaign response result affected


I would have no concerns about sorting a list of < 100 items twice, rather than once, in a single email assembly. The overhead is infinitesimal.

 

However, sending 1,000,000 emails at once is a decision not to be taken lightly, regardless of what Velocity functions you call. Be prepared to be throttled and/or to have a high bounce rate, nothing to do with VTL.

View solution in original post