Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Email Preview Error - Using a Seed Address

Avatar

Avatar
Validate 10
Level 3
holmes74338504
Level 3

Likes

17 likes

Total Posts

51 posts

Correct Reply

5 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile

Avatar
Validate 10
Level 3
holmes74338504
Level 3

Likes

17 likes

Total Posts

51 posts

Correct Reply

5 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile
holmes74338504
Level 3

08-04-2020

Hello, 

 

Trying to generate a email preview and I get the same error - 

 
 

error.png

 

Here's the variable I have coded in the email: 

 

var effectiveDate = targetData.effectiveDate

 

And I'm calling it into the email as: <%=formatDate (effectiveDate, "%Bl %D") %>

 

The seed I'm using is set-up with effectiveDate in the 'Additional Fields' tab: 

seed.JPG

 

I tried changing that Date format to : "2020-04-07" and "2020-04-07 12:00:00.177Z" - both formats still gave me the same error. 

 

I am on Adobe Console - v7 build 8895

Can anyone help why I would get this error when generating a Preview?

 

FYI - when I send the email to a select test group - the email delivers fine with no errors. 

 

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
MVP
Darren_Bowers
MVP

Likes

75 likes

Total Posts

253 posts

Correct Reply

81 solutions
Top badges earned
Validate 1
Affirm 50
Establish
Give Back 3
Applaud 25
View profile

Avatar
Validate 1
MVP
Darren_Bowers
MVP

Likes

75 likes

Total Posts

253 posts

Correct Reply

81 solutions
Top badges earned
Validate 1
Affirm 50
Establish
Give Back 3
Applaud 25
View profile
Darren_Bowers
MVP

08-04-2020

formatDate() requires a Date object and in your additional data, date is a string, which will generate that error. I would say your targetData normally has an actual date object for effectiveDate which is why it works when you run the workflow.

Answers (0)