AnsweredAssumed Answered

How can I send 1 email with dynamic content blocks for products they have and products they don't have?

Question asked by Ronn Burner on Nov 10, 2019
Latest reply on Dec 6, 2019 by Sanford Whiteman

Like • Show 2 Likes2
Comment • 79

Here is what I'm being told from above that I need to solve for. I can't figure this out.

Think of our product model as DirecTV. A customer can go online and select (subscribe) to any channel or combination of channels they choose. - - So I have 10 ala carte products and a new subscriber signs up to any 1 single product or any number combination up to all 10 products. I only want ONE email to be sent per new subscriber regardless of how many products they subscribed to at one time. Then I will send a 2nd email later. Is it possible - and practical - to acknowledge each product they subscribed to uniquely with a text block and/or image for each AND a different text block promoting the products they did not subscribe to? And if not, what is the best way to handle this type of situation?

So many questions: 1. Segmentation logic? 2. Snippets, dynamic emails or unique streams or programs? 3. Engagement or Default Programs? 4. How to ensure ONLY 1 email regardless of new subscriptions deploys? 5. Smart campaign total and goal?

Any thoughts and or advice on how to handle this initial entry via new subscribers would be a life saver. Thank you!

Sanford Whiteman Dec 2, 2019 11:16 PM

Correct Answer

- I should only use $lead.DMSSubscribed or $lead.DMSSubscribedDate and not both, right?

Only the DateTime field.

- Do I simply just replace all $lead.DMSSubscribed with $lead.DMSSubscribedDate in the code?

Yes, that is, if you're going to convert a stringified DateTime (i.e., ISO8601 format) field into a Date, that's where you use the DateTime.

However I don't think these are ISO8601 "yyyy-MM-dd'T'HH:mm:ss". They're actually ISO8601 "yyyy-MM-dd HH:mm:ss". That is, they have a space instead of the letter "T". So you can add this line to the code at the top:

#set( $ISO8601WithSpace = "yyyy-MM-dd HH:mm:ss" )

Then use $ISO8601WithSpace where you're using $ISO8601 now.

Parsing a String to a Date requires that you tell Velocity (actually Java) all the parts of the format.

- Do I uncheck the $lead.DMSSubscribed box in the Script Token?

For clarity, yes, but it's harmless to leave it checked as you won't be using it. Leaving it unchecked means it will always have the value null. That may be more or less confusing if you accidentally use it, I don't know.

See the reply in context

No one else had this question

Outcomes

79 Replies

Ronn Burner Nov 10, 2019 1:03 PM
Mark Correct
Correct Answer
Jay Jiang
You have saved my life before so I always like to check in with you to set me straight.
Like • Show 0 Likes0
Actions
- Jay Jiang @ Ronn Burner on Nov 10, 2019 2:48 PM
  Mark Correct
  Correct Answer
  As Sandford says, use a velocity script that dynamically adds blocks of text if respective checkbox is ticked.
  
  To have the email sent once, I assume your sign up form triggers a Filled out Form or Person is pushed to Marketo trigger? Send the email in the flow of that smart campaign.
  Like • Show 1 Like1
  Actions
  - Ronn Burner @ Jay Jiang on Nov 10, 2019 5:31 PM
    Mark Correct
    Correct Answer
    I responded to Sanford below and as you can see, sadly, I'm not going to be able to do this without a significant amount of help. I'm sure this is not a part of your job description and I'm aware it's asking a lot. I would certainly understand if either of you weren't interested in helping me.
    
    Now knowing velocity is the answer this is no longer an issue. My trigger would be based on the Data Value Change of PRODUCT A SUBSCRIBED = TRUE and in the flow (or stream if this becomes Engagement Program) it would just send the 1 email.
    Like • Show 0 Likes0
    Actions
Sanford Whiteman Nov 10, 2019 1:45 PM
Mark Correct
Correct Answer
What is a product subscription stored as? An individual Boolean? An individual DateTime? An entry in a semicolon-delimited list?
Like • Show 0 Likes0
Actions
- Ronn Burner @ Sanford Whiteman on Nov 10, 2019 2:20 PM
  Mark Correct
  Correct Answer
  Individual boolean custom field per product. I have a custom CRM so was previously required to make those fields to utilize in other Up-sell program and get away from "Added to" and "Has updated" custom object world.
  Like • Show 0 Likes0
  Actions
  - Sanford Whiteman @ Ronn Burner on Nov 10, 2019 2:38 PM
    Mark Correct
    Correct Answer
    This isn't a case for segmentations, then. Too many permutations. (Even if you could precompute them, you don't have enough segments.)
    
    The answer: Velocity. VTL can easily check the value of a Boolean. (Many of my blog posts are about working with Boolean/Boolean-like/once-Boolean values, since it's the most important datatype to understand when using #if!)
    Like • Show 2 Likes2
    Actions
    - Ronn Burner @ Sanford Whiteman on Nov 10, 2019 5:22 PM
      Mark Correct
      Correct Answer
      This is so disheartening. I read the blog posts you linked to and it's far too complex for me. I have no experience with velocity. It's so confusing and I'm afraid I'm just not intelligent enough to do this on my own. I need hand holding to do this level of work within Marketo. As you say, I'm sure this is easy and certainly easy for you but it's a foreign language to me. Is there a way to get me through this - here step by step or offline if that's less annoying?
      Like • Show 0 Likes0
      Actions
      - Jay Jiang @ Ronn Burner on Nov 10, 2019 6:44 PM
        Mark Correct
        Correct Answer
        Trust me, the looping nurture program you set up is far more complex than creating an email script.  Don't fear what is unfamiliar. And I apologise for seeming to trivialise it.
        
        Maybe Sanford Whiteman can give you a helping hand with the code!
        Like • Show 1 Like1
        Actions
        Sanford Whiteman @ Jay Jiang on Nov 10, 2019 7:36 PM
        Mark Correct
        Correct Answer
        Agreed, Jay!
        
        Admittedly, it can feel good when your area of expertise is intimidating to others -- then you know it's a real skill. On the other hand, nothing is impossible... it may have taken many hours to get to an advanced level, but surely someone else can do it given enough time + enthusiasm. (I have one official student now, we'll see how that goes!)
        
        Having at least a passing knowledge of VTL -- that's "Velocity Template Language" by the way, the full name of the language but interchangeable w/"Velocity" -- is critical to getting (seemingly) run-of-the-mill tasks done in Marketo. And, to be frank, it's great for your career (bringing Velocity into a place that never used it makes you a hero)
        
        In this case, you're talking about a bunch of special Strings in Velocity (corresponding to Booleans in Field Management) that each have one of two values: "1" (true-like) or "" (false-like). And you want to choose output based on the value.
        
        Let's say 2 of the fields, checked off in the fields tree in Script Editor, are $lead.product1 and $lead.product2.
        
        A basic Velocity snippet to do content switching looks like this:
        
        #if( $lead.product1.equals("1") ) You subscribed to Product 1. #else You did not subscribe to Product 1. #end #if( $lead.product2.equals("1") ) You subscribed to Product 2. #else You did not subscribe to Product 2. #end
        
        The output lines are text-only for readability, but can just as easily be HTML.
        
        (Granted I would probably do this in a slightly slicker way myself, but this way is easiest to understand.)
        2 people found this helpful
        Like • Show 8 Likes8
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 11, 2019 9:44 AM
        Mark Correct
        Correct Answer
        Jay, that is good to hear. And you nailed it - I panicked in terror due to the unfamiliarity. Just when I think my Marketo game is solid something like this presents itself and I feel like it's my first day in the instance.
        
        Sanford, I look forward to being a hero. Trust me! This stuff is exhilarating to learn once the "Aha!" moment clicks - and the terror subsides. I've been reading your content for years - Your student is lucky to have you!
        
        I have created this 'Email Script' token implementing the boolean field 'Product X Subscribed' for our 7 products (there will be more to come later but at this point we have only these 7.)
        
        Am I headed down the right path thus far? I don't want to get to far ahead but just to see if I'm even remotely close to comprehension here 1.) In the end, will this be a token in the email HTML? 2.) Is this only the dynamic content block to pull in information for those products that were, in fact, subscribed to which means I would need to duplicate this script using .equals("") ) for the content block of the products they did not subscribe to?
        
        I'm probably overthinking it because if it does not equal ("1") then obviously it equals ("")
        
        And we're off! I CAN DO THIS! I think I can... I think I can... I think I can...
        Like • Show 2 Likes2
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 11, 2019 10:52 AM
        Mark Correct
        Correct Answer
        Am I headed down the right path thus far?
        Yep!
        
        1.) In the end, will this be a token in the email HTML?
        Yes, you will include the name of the {{my.token}} in the email.
        
        2. Is this only the dynamic content block to pull in information for those products that were, in fact, subscribed to
        No, you're including content for both the true and false fields here.
        
        If you want to break it up with all trues first, then all falses second, then have
        #if( $lead.field1.equals("1") ) Your field1 is true. #end #if( $lead.field2.equals("1") ) Your field2 is true. #end #if( $lead.field1.equals("") ) Your field1 is true. #end #if( $lead.field2.equals("") ) Your field2 is true. #end
        1 person found this helpful
        Like • Show 2 Likes2
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 11, 2019 11:20 AM
        Mark Correct
        Correct Answer
        If you want to break it up with all trues first, then all falses second, then have
        I'm open to suggestions on how to best do this but in my mind (because I wasn't sure how else to make it work) I saw this as 10 individual content blocks and if you sign up for 1 product it only populates that 1 block "Welcoming" them. The other 9 blocks are then the remaining products they did not subscribe to Or if you subscribe to 7 you get "welcomed" from each of them and still pitching the 3 products they did not subscribe to.
        
        So for every product subscription that = TRUE the block will have "Welcome/Confirmation" text and/or image populate it and those that = FALSE will have "You still need this product blah blah" text.
        
        I think perfect world I would love to acknowledge each product they subscribed to (1 to 10) at once AND only 3 of the products they still need to subscribe to - rather than all 9 if they only subscribed to a single product.
        
        I'm sure you can see a clear best way to do this with how Velocity within Marketo works - and i am 100% open to it. In the end I just need to acknowledge/confirm what they DID subscribe to AND mention at least a couple products they have NOT subscribed to.
        
        I'm all ears and eager as can be to learn! And I cannot thank you enough for your help, time and patience! it is beyond appreciated.
        Like • Show 1 Like1
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 11, 2019 2:48 PM
        Mark Correct
        Correct Answer
        In the end I just need to acknowledge/confirm what they DID subscribe to AND mention at least a couple products they have NOT subscribed to.
        As far as I can see, you have exactly that already.For each product, you have the choice to output certain content if their value is "1" (they are subscribed to that product) or if their value is "" (they are not subscribed to that one).
        
        You can do all the "welcomes" first. Only output the welcome for a product if it is subscribed ("1").
        
        Then do all the "pitches". Only print the pitch for a product if it is not subscribed ("").
        1 person found this helpful
        Like • Show 2 Likes2
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 11, 2019 4:52 PM
        Mark Correct
        Correct Answer
        You will be shocked at the stupidity of this question so I apologize in advance BUT where is the content being pulled from to populate the "1" and "" within the body of the email?
        
        If Product X Subscribed = "1" that area will populate with the paragraph and/or image specific to that product but where is that built and stored to be pulled from? I know the answer is right in front of my face yet I don't know it.
        
        After I figure that part out. Then am I to simply have a single content block with the Email Script Token {{my.VelocityAllTrueThenAllFalse}} or do I put that token in 8 (1 for each product) different blocks (there are 8 actually, I misspoke and said 7 previously) or since there is a "1" and a "" do I need a total of 16 block with the token in each?
        
        I believe I have this correct in the below image?
        Like • Show 1 Like1
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 11, 2019 6:35 PM
        Mark Correct
        Correct Answer
        If Product X Subscribed = "1" that area will populate with the paragraph and/or image specific to that product but where is that built and stored to be pulled from?
        It's built right where you currently have "Your Max Digital Subscribed is true" and so on. Replace that with your actual content, including HTML <div>/<img>/<whatever> tags.
        
        Then am I to simply have a single content block with the Email Script Token {{my.VelocityAllTrueThenAllFalse}}
        You'd embed the {{my.token}} only once. It does all the output, covering all the permutations.
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 12, 2019 9:03 AM
        Mark Correct
        Correct Answer
        Got it. I figured it would have to be but I made it way more difficult than I needed to. After seeing this and having that "click" moment really makes re-reading your blog posts actually seem like English. This is very, very cool and skill and knowledge I will continue to to explore and sharpen. Now I want to do this for ALL my automation emails!
        
        I can see this is simple and very flexible to simply add, subtract or edit any product in the token - which will be tremendously helpful as our products are software and are constantly changing.
        
        After reviewing how this process will work I realized I have an additional question. All new subscriptions for any product triggers this email.
        As it is now, a lead signs up for new Subscription for 1 to 8 products that triggers this email scanning all the "1" and "" and populating each products content as it should. However, it's very common that a client will, in fact, subscribe to one of the remaining products they do not yet have on any later date, in which case would once again trigger this same email - which would scan and once again "Welcome" them to a product they already have. You see what I mean.
        
        How should I - or how would you handle that?
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 12, 2019 12:55 PM
        Mark Correct
        Correct Answer
        Here's where people realize that Booleans are (usually) an inferior substitute for DateTimes.
        
        A non-empty DateTime is effectively a superset of a Boolean, because it indicates both (a) that something is true and (b) when it became true. In contrast, as you're finding out, a Boolean can only record whether something is currently true or false.
        
        If you had these as DateTimes you could find out the ones that became true during the past day and only "welcome" those. Of course that means more advanced Velocity code.
        
        P.S. In the the grander scheme of database design, people know Booleans are resource-efficient, so they don't reach out to DateTimes as fast as they should IMO. It's true that a Boolean can take up only a byte, or even less, while a DateTime takes 6-8 bytes to store -- but still not worth worrying about unless you're talking hundreds of fields and have proven that storage is a real-world concern.)
        1 person found this helpful
        Like • Show 2 Likes2
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 12, 2019 1:49 PM
        Mark Correct
        Correct Answer
        Right. I see. Well, we may be okay then - Thanks to Jay back when I created my dynamic programs - he advised the DateTime approach so I did, in fact, add a custom field "Product X Subscribed Date" to go along with the boolean T/F. I used {{system.date}} simply because our CRM to Marketo sync is a one way street daily batch so Time becomes irrelevant. Understanding this better I now see that is information I should have provided to you at the top. My apologies.
        
        Now, that being said, if that works, can you help me get there or does "more advanced Velocity code" translate to "forget about it!?"
        
        All this information is invaluable and I'm eagerly absorbing it.
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 12, 2019 1:58 PM
        Mark Correct
        Correct Answer
        You would start with the seminal post on day/time in Velocity: https://blog.teknkl.com/velocity-days-and-weeks/
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 12, 2019 7:28 PM
        Mark Correct
        Correct Answer
        ... add a custom field "Product X Subscribed Date" to go along with the boolean T/F.
        But if you're not also updating the DateTime when someone flips to false, then there's no need for the Boolean. I'm talking about having only a DateTime, not both.
        
        On the other hand, if the DateTime also is updated on the Unsubscribed Date -- functioning as the Last Product X Subscription Change Date as opposed to only the Last Product X Subscribed Date -- then you do need the 2 fields, since that can't be reflected with just the DateTime.
        1 person found this helpful
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 15, 2019 7:57 AM
        Mark Correct
        Correct Answer
        Thanks for following up because I read your blog post several times and realized I don't know near enough yet to proceed. So thank you for not abandoning me. This is an invaluable lesson and experience to add to my skill set.
        But if you're not also updating the DateTime when someone flips to false, then there's no need for the Boolean.
        I am actually. If Product X gets 'Canceled', it is System.Date stamped and 'Product X Subscribed' changes to False. The custom fields I created (again per Jay Jiang many months ago - I keep giving him credit because he went above and beyond to help me and he deserves it to be acknowledged for it) are:
        
        Product X Subscribed (Boolean)
        Product X Subscribed Date (System.Date)
        Product X Canceled Date (System.Date)
        Product X Nurture Completed (Boolean) - which is used to complete loop program and reset to re-enter later
        I'm talking about having only a DateTime, not both.
        Right. I see. It's not necessary as the system.date stamp (value) - if there is one - for Subscribed/Canceled lets you know the TorF status of each.
        
        I feel like all of what I have is good news and we're still in business since we have this data in place already, right?
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Ronn Burner on Nov 15, 2019 11:21 AM
        Mark Correct
        Correct Answer
        Based on the fields I have am I able to create more advanced Velocity code required to "welcome" those that became true during the past day? If so, how?
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 15, 2019 11:29 AM
        Mark Correct
        Correct Answer
        During the past 24 hours? Or during the current calendar day in your timezone? (Different things)
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 15, 2019 11:38 AM
        Mark Correct
        Correct Answer
        The past 24 hours because these 'statuses' change in the CRM and there's only a single daily sync to Marketo. Obviously causing all DateTime/system.dates to match for that day regardless of when it really took place. Therefore all 'Data Value Change' triggers fire at the sync - so I typically just batch all yesterdays data to take action today.
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 15, 2019 11:44 AM
        Mark Correct
        Correct Answer
        OK, then you'd need to use the DateTime math code from https://blog.teknkl.com/velocity-days-and-weeks/. It's too far afield for this post, you really need to know Velocity to support complex code like that in the long term.
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 15, 2019 12:15 PM
        Mark Correct
        Correct Answer
        In other words use only Product X Subscribed = "".
        
        Will DateTime recognize system.date since that is the field I created? And the blog post touches on coding scenarios different than this particular one. The TimeZone one is closest but still not interchangeable.
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 15, 2019 9:04 PM
        Mark Correct
        Correct Answer
        Will DateTime recognize system.date since that is the field I created?
        I don't understand the question...
        
        And the blog post touches on coding scenarios different than this particular one. The TimeZone one is closest but still not interchangeable.
        Actually all those recipes involve timezones -- because all Dates have timezones.
        
        The difference in hours between 2 Dates follows the framework in Use Email Script Token to calculate number of years based on a date field (itself adapted from my main blog post) only you'd use getHours() instead of getYears(). Like:
        
        #set( $calProductXSubscribed = $convert.toCalendar( $convert.parseDate(     $lead.ProductXSubscribed,     $ISO8601,     $defaultLocale,     $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calProductXSubscribed).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 18, 2019 11:29 AM
        Mark Correct
        Correct Answer
        I don't understand the question...
        In the 'Product X Subscribed Date' and 'Product X Canceled Date' custom fields I created I populated that value with {{system.date}} rather than {{system.dateTime}} and I was wondering if that mattered in this particular case.
        only you'd use getHours() instead of getYears(). Like:
        I have created and duplicated 8 times (specific to each product) this exact framework in the Email Script Token. I assume I need to have these 8 product specific blocks followed by the 8 false blocks like so:
        #if( $lead.DMSSubscribed.equals("") )
        Your DMS Subscribed is false.
        #end
        Am I missing anything or is this 100% completed and ready to go once I fill in the messaging?
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 18, 2019 11:50 AM
        Mark Correct
        Correct Answer
        In the 'Product X Subscribed Date' and 'Product X Canceled Date' custom fields I created I populated that value with {{system.date}} rather than {{system.dateTime}} and I was wondering if that mattered in this particular case.
        Then you probably got midnight on that day stored in the DateTime, which certainly matters as it could be up to 23 hours and 59 minutes off.
        
        I have created and duplicated 8 times (specific to each product) this exact framework in the Email Script Token. I assume I need to have these 8 product specific blocks followed by the 8 false blocks like so:
        #if( $lead.DMSSubscribed.equals("") )
        Your DMS Subscribed is false.
        #end
        Yes. But you should also wrap the first set of conditions in a not-equals check, so you ensure that you don't try to convert an empty string to a Calendar (this will non-fatally fail but should be avoided).
        
        #if( !$lead.ProductXSubscribed.isEmpty() ) #set( $calProductXSubscribed = $convert.toCalendar( ## etc., etc. #end
        
        Am I missing anything or is this 100% completed and ready to go once I fill in the messaging?
        Sorry but I really can't sign off on your implementation, never having looked at it in reality. Once you put it through its paces, testing a representative set of cases, it's good to go.
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 18, 2019 1:08 PM
        Mark Correct
        Correct Answer
        So this issue has been resolved. I just updated all {{system.date}} flow steps in entire instance with {{system.dateTime}} so the times will all match in the daily CRM-Marketo sync.
        Yes. But you should also wrap the first set of conditions in a not-equals check
        This image is the snapshot of the transition from Product 8 to the not-equals check.
        
        Sorry but I really can't sign off on your implementation
        I understand that and I will certainly test once I at least "think" I have the script correct. For example, if this image is correct I can move in that direction, however, I'm not certain you meant to script it the way I have here or if you meant something else.
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 18, 2019 1:29 PM
        Mark Correct
        Correct Answer
        That's not valid VTL, it will throw a fatal error instantly as you'll see in Preview.
        
        I'm saying you need to wrap the entire Calendar creation in an isEmpty() check. The #etc., etc. represents where you'd put your existing code. You're adding a precondition around it, also called a guard.
        
        #if( !$lead.ProductXSubscribed.isEmpty() ) #set( $calProductXSubscribed = $convert.toCalendar( $convert.parseDate(     $lead.ProductXSubscribed,     $ISO8601,     $defaultLocale,     $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calProductXSubscribed).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 18, 2019 2:24 PM
        Mark Correct
        Correct Answer
        Got it. I think. This now has the first set of conditions wrapped per product for an isEmpty() check. Then following the Calendar creation and guard I then transition into the #if( $lead.ProductXSubscribed.equals("") ) check to send that appropriate messaging.
        This image transition from Product 8 into still yet to Subscribes.
        
        I believe that is now accurate and correct. But in my email test sends I don't see anything populating. Where exactly do I place the {{my.VelocityTimeZone}} token?
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 18, 2019 2:38 PM
        Mark Correct
        Correct Answer
        You can't send samples to test Velocity, you must send real emails
        You don't need to send emails at all, using Preview-by-List with a static List (add a few representative leads) is the only way to stay sane while troubleshooting Velocity code
        Please don't call this token {{my.VelocityTimeZone}}, it doesn't have anything do with the purpose/output; variables should have accurate + complete names, {{my.RecentlySubscribedProducts}} for example
        You'd put the token in the body of an email, as with other {{my.tokens}} (or in theory in the Subject line, but presumably this content is designed for the body)
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 18, 2019 3:50 PM
        Mark Correct
        Correct Answer
        I've done everything you suggested. The email Preview-by-List view does not populate the token. And just after I felt soooo close. Bummer. Is this an indication of the VTL being broken somewhere or what could be causing this?
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 18, 2019 10:34 PM
        Mark Correct
        Correct Answer
        You'll have to add some debugging lines. If you just put
        
        ${display.list( $lead.entrySet(), "\u000a" )}
        
        on a line by itself, that will show you what the lead object looks like in raw form. Go to the Text version of the email to look at the output, then you can post a screenshot.
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 19, 2019 8:49 AM
        Mark Correct
        Correct Answer
        This was the result of that line.
        
        Interestingly in a different email template I used for testing it rendered differently. And I should note this version is the actual template this emails will be built from.
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 19, 2019 10:23 AM
        Mark Correct
        Correct Answer
        Do you have the required fields checked off in the tree on the right-hand side of Script Editor? Sure doesn't look like it.
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 19, 2019 1:00 PM
        Mark Correct
        Correct Answer
        Nope. I had no clue. Sorry. Your level of frustration must be approaching record levels.
        I checked all 8 Product Subscribed and all 8 Product Subscribed Date only. Is that correct?
        Here is the result of that...
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 19, 2019 1:06 PM
        Mark Correct
        Correct Answer
        That's better, but you said they were DateTimes... those are stringified Date fields.
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 19, 2019 1:22 PM
        Mark Correct
        Correct Answer
        Yes. Ugh. I need to create all new custom fields with type set to' Datetime'... these were built as 'Date' apparently. I simply changed the {{system.date}} token to {{system.dateTime}} in the flow step that writes that data when the Subscription takes place.
        
        Obviously I can build the appropriate new 'Product X Subscribed Date' (times 8) custom fields moving forward but what suggestions do you have to remedy those records already populated with a 'Date'?
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 19, 2019 1:37 PM
        Mark Correct
        Correct Answer
        Yes, a flow step cannot change the datatype (think about who can add flow steps vs. who has access to Field Management and this will surely make sense).
        
        You don't need to create 8 new fields. You should be able to create 1 new, temporary Date field to hold old values while you change each existing Date to a DateTime, one at a time.
        
        Converting a field is a destructive act. So you first copy, for example, oAPSubscribedDate to your temporary Date field using Change Data Value. Then convert the datatype for just that one field. Then copy the temporary field back to the changed oAPSubscribedDate.
        
        Then clear all the values of the temporary field. Now the temporary field is ready for reuse. Repeat for cRMProSubscribedDate, copying to the temp field, changing the datatype of the real field, and copying the data back.
        
        Or export all your values to CSV, together with the email address of course, change all the datatypes (which destroys all current values) and reimport the CSV. This wouldn't even require a temp field.
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 19, 2019 2:18 PM
        Mark Correct
        Correct Answer
        I've run into this in the past. I've selected the custom field then the 'Field Actions' > Change Type and this is what happens.
        In order to change the type after I export CSV will I then need to go into all locations for each 'Product X Subscribed Date' and remove from each program/list? I like your way better to have the option to simply change the type and destroying current values and then importing new values.
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 19, 2019 2:35 PM
        Mark Correct
        Correct Answer
        Whatever you do is going to require un-using the current field, either temporarily or permanently.
        
        If you switch to 8 new fields then you need to switch all the places the old fields were used.
        
        If you use the temp field then you need to temporarily switch all the places the old field was used, as you swap the values.
        
        There's no way around needing to touch all the places the field is used.
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 20, 2019 12:08 PM
        Mark Correct
        Correct Answer
        Understood. Just wanted to confirm.
        
        I haven't forgotten about this but in the process of exporting to CSV I discovered that 'Product X Subscribed Date' per product is updating daily to that day. So all leads Subscribed Dates are today. Obviously a major problem I need to resolve asap.
        This is occurring due to this Smart Campaign (below). I'm unclear as to what specific action needs to take place to qualiify for “Was Added to Product Revised” (the 002 New (Daily) Subscriptions (Trigger) Campaigns in the tree) versus what action qualifies as “Has Product Revised” - the 001 Batch campaigns.
        It appears the one time daily sync is causing this Smart Campaign to read that data as new and update the 'Subscribed Date' to the current day.
        You wouldn't happen to clearly be able to see precisely what the problem is would you?
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 20, 2019 3:51 PM
        Mark Correct
        Correct Answer
        Those filters refer to Custom Objects.
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 20, 2019 5:23 PM
        Mark Correct
        Correct Answer
        Only Filter 1 Has Products Revised and 4 DCID are Custom Objects. Dealership Account Status is a Custom Field. I don't know what you mean in terms of identifying that as being a problem or "thee" problem. That Smart Campaign should work in my mind by writing the Product X Subscribed Date one time on the day it takes place and it remains that datetime. What do I need to do to accomplish that?
        
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 20, 2019 5:47 PM
        Mark Correct
        Correct Answer
        You can't read the field subscribedOn from the Custom Object in a flow, if that's what you mean. It is not accessible as a token in that context, only in Velocity.
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 21, 2019 7:33 AM
        Mark Correct
        Correct Answer
        That's not exactly what I'm doing but your point may still stand. Let me explain and then advise accordingly.
        I am actually not using the Custom Object subscribedOn field in the flow - that field and many having to do with our CRM have been very problematic as it was implemented prior to my arrival with little planning complicating the Marketo integration tremendously.
        
        Rather what I've done is converted the Custom Object into a custom field on the lead record. Just "flattened" out the CO with the custom field 'DMS Subscribed' into a boolean True or False when "Status" (a CO attribute) = 'Subscribed'.
        'DMS Subscribed Date' with the token is also a custom field on the lead record - which does work. I believe all of that is done completely correct. As a matter of fact, I'm almost certain this was your solution (I could be wrong though) I found here in the community and built a couple years ago.
        
        Assuming that is correct, and in fact, this is the Smart Campaign rewriting the date every day. So the flow is working. The Smart List is the problem in that it's doing exactly what it is told but am I telling it incorrectly?
        
        Is it scanning every day for ALL records 'Subscribed' to 'Dealer Desktop (DMS)' plus the filters and then pushing them through the flow - which is updating their 'DMS Subscribed Date' with the daily sync? That sure seems to be the case. If so, how can I remedy that? I didn't think this would happen because if the data value is NOT changing in the CRM (after the one time) then it should not sync and overwrite again UNTIL the value changes to "unsubscribed".
        
        What is the difference between the two Custom Objects: "Added to..." and "Has..." - in terms of what action qualifies for each? I created a Trigger campaign for "Added to..." (thinking it meant catching NEW) and this Batch campaign for "Has..." (thinking it was catching UPDATED). One problem I see is in the Campaign Schedule I'm allowing the lead to run through the flow every time - changing that to only once may solve it all. Oh my goodness, can it be that easy?
        
        Please correct me if I'm wrong.
        I can see that I can correct all of this as well as properly implement the Velocity that began this conversation I just want to ensure with your guidance I get to the desired result properly.
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 25, 2019 11:23 AM
        Mark Correct
        Correct Answer
        I have successfully changed the datatype for the custom fields and appropriately checked all the 'Product X Subscribed' (Boolean T/F) and 'Product X Subscribed Date' (DateTime) boxes in the Script Token. I think everything is where it needs to be to move forward now. This is how the preview-by-list appears (below).
        Am I missing any other boxes to check and/or where do I need to go from here? Thank you.
        
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 25, 2019 12:14 PM
        Mark Correct
        Correct Answer
        It appears you have changed the field type to DateTime successfully, at least for those fields that have a value shown here (if the value is empty you can't tell what the original field type is).
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 25, 2019 1:20 PM
        Mark Correct
        Correct Answer
        The empty values are supposed to reflect Product X Subscribed = False. I can confirm though that I have changed the datatype from Date to DateTime for all Product X Subscribed Date fields.
        I have updated my record (below image) and intentionally left 'Dealer Websites Subscribed' as empty (false) and 'CRM Pro Subscribed Date' as empty to see what we see.
        I did notice in spot checking that there are a small number of records in the data base that do, in fact, have current subscriptions but with an empty 'Subscribed DateTime'. I can remedy that with a Smart Campaign for those such records with 'Product X Subscribed' = True AND 'Product X Subscribed Date' is empty to write in some static value I determine just so there is a value there.
        Am I on the right track or what do you see I need to still do to get on the right track?
        
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 25, 2019 1:32 PM
        Mark Correct
        Correct Answer
        Yes, was talking about the empty values for the fields that have "Date" in the name. From the name alone I can't tell you whether those are Dates or DateTimes. Not saying you didn't do the datatype change correctly, merely that I can't confirm that you did using just the screenshot.
        
        You appear to be on the right track overall.
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 25, 2019 2:28 PM
        Mark Correct
        Correct Answer
        Yes, I unfortunately and dare I say stupidly changed the datatypes without changing the name to reflect DateTime rather than just Date.
        That said, I have just now changed the names of the fields from 'Product X Subscribed Date' to 'Product X Subscribed DateTime', however, the email preview is identical to the above screenshot. It didn't change from Date to DateTime in the preview but the proper name is refelected in the Script Token checkbox field tree. What clear and obvious thing am I missing and/or did I do wrong?
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 25, 2019 3:42 PM
        Mark Correct
        Correct Answer
        The Velocity property name won't change, you're only changing the friendly name.
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 26, 2019 6:34 AM
        Mark Correct
        Correct Answer
        So that's correct. I have the datatypes now correctly set. Checkmarked the Script Editor boxes for 'Subscribed' and 'Subscribed DateTime' for each product. Placed the token in an email. previewed-by-list and actually sent the email through a Smart Campaign but when received the token block is completely blank.
        It feels like it's sooo close but then again without having comprehensive knowledge I may not even be close yet.
        Please let me know of my next step? Here is the complete VTL.
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 26, 2019 8:50 AM
        Mark Correct
        Correct Answer
        Pls provide the code in a way that I can test it (text, highlighted as Java).
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 26, 2019 11:07 AM
        Mark Correct
        Correct Answer
        I've copied it but indents and spacing are off so I've also attached it as is via notepad.
        
        ${display.list( $lead.entrySet(), "\u000a" )} #if( !$lead.DMSSubscribed.isEmpty() ) #set( $calDMSSubscribed = $convert.toCalendar( $convert.parseDate(     $lead.DMSSubscribed,     $ISO8601,     $defaultLocale,     $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calDMSSubscribed).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.CRMSubscribed.isEmpty() ) #set( $calCRMSubscribed = $convert.toCalendar( $convert.parseDate(     $lead.CRMSubscribed,     $ISO8601,     $defaultLocale,     $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calCRMSubscribed).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.BHPHSubscribed.isEmpty() ) #set( $calBHPHSubscribed = $convert.toCalendar( $convert.parseDate(     $lead.BHPHSubscribed,     $ISO8601,     $defaultLocale,     $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calBHPHSubscribed).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.AutoCheckSubscribed.isEmpty() ) #set( $calAutoCheckSubscribed = $convert.toCalendar( $convert.parseDate(     $lead.AutoCheckSubscribed,     $ISO8601,     $defaultLocale,     $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calAutoCheckSubscribed).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.OAPSubscribed.isEmpty() ) #set( $calOAPSubscribed = $convert.toCalendar( $convert.parseDate(     $lead.OAPSubscribed,     $ISO8601,     $defaultLocale,     $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calOAPSubscribed).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.DealerWebsitesSubscribed.isEmpty() ) #set( $calDealerWebsitesSubscribed = $convert.toCalendar( $convert.parseDate(     $lead.DealerWebsitesSubscribed,     $ISO8601,     $defaultLocale,     $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calDealerWebsitesSubscribed).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.CRMProSubscribed.isEmpty() ) #set( $calCRMProSubscribed = $convert.toCalendar( $convert.parseDate(     $lead.CRMProSubscribed,     $ISO8601,     $defaultLocale,     $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calCRMProSubscribed).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.MaxDigitalSubscribed.isEmpty() ) #set( $calMaxDigitalSubscribed = $convert.toCalendar( $convert.parseDate(     $lead.MaxDigitalSubscribed,     $ISO8601,     $defaultLocale,     $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calMaxDigitalSubscribed).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( $lead.DMSSubscribed.equals("") ) Your DMS Subscribed is false. #end #if( $lead.CRMSubscribed.equals("") ) Your CRM Subscribed is false. #end #if( $lead.BHPHSubscribed.equals("") ) Your BHPH Subscribed is false. #end #if( $lead.AutoCheckSubscribed.equals("") ) Your AutoCheck Subscribed is false. #end #if( $lead.OAPSubscribed.equals("") ) Your OAP Subscribed is false. #end #if( $lead.DealerWebsitesSubscribed.equals("") ) Your Dealer Websites Subscribed is false. #end #if( $lead.CRMProSubscribed.equals("") ) Your CRM Pro Subscribed is false. #end #if( $lead.MaxDigitalSubscribed.equals("") ) Your Max Digital Subscribed is false. #end
        Attachments
        Ronn Burner VTL.txt.zip652 bytes
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 26, 2019 10:56 AM
        Mark Correct
        Correct Answer
        Pls highlight using the Syntax Highlighter as well.
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 26, 2019 11:09 AM
        Mark Correct
        Correct Answer
        Got it. I never knew how that was done in the community. This has been such an important lesson for me. Thanks. I edited my previous comment.
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Nov 29, 2019 7:19 AM
        Mark Correct
        Correct Answer
        Just following up with this in the event you missed it. Though enjoying Thanksgiving time off is more likely and well deserved. I have edited and used the Syntax Highlighter in my previous comment with the entirety of the VTL for your review.
        
        Thank you kindly and I hope you and yours have/had a very Happy Thanksgiving weekend!!
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Nov 30, 2019 9:30 PM
        Mark Correct
        Correct Answer
        If that's your full code, it's missing the common snippet from the top of my Day/Time blog post. (For example, it refers to the variable $ISO8601 which doesn't exist without that snippet included.)
        
        It's also confusing $lead.DMSSubscribed and $lead.DMSSubscribedDate (and all the other pairs of values). The first is a Boolean ("1" or "" in Velocity). The second is your stringified DateTime, which is the one you need to convert to a Date in Velocity.
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Dec 2, 2019 8:46 AM
        Mark Correct
        Correct Answer
        That was the full code - but now I have added those 7 lines of code at the top as well as "Los_Angeles" rather than "New_York" - which I assume is fine.
        It's also confusing $lead.DMSSubscribed and $lead.DMSSubscribedDate (and all the other pairs of values). The first is a Boolean ("1" or "" in Velocity). The second is your stringified DateTime, which is the one you need to convert to a Date in Velocity.
        If your confused by what I've done just imagine how exponentially more lost I am. And remember, this whole time I felt confident I was doing exactly what you had been advising. Clearly not the case. I feel like I'm stuck in a riddle.
        I can read your diagnosis - and on a macro level understand the root of the problem - but I'm unclear of the remedy as there appears to be numerous implications and paths from one to several changes required or any combination thereof.
        
        I'll be succinct and methodical for clarity (mine, not yours ):
        
        - I should only use $lead.DMSSubscribed or $lead.DMSSubscribedDate and not both, right?
        - Do I simply just replace all $lead.DMSSubscribed with $lead.DMSSubscribedDate in the code?
        - Do I uncheck the $lead.DMSSubscribed box in the Script Token?
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Dec 2, 2019 11:16 PM
        Unmark Correct
        Correct Answer
        - I should only use $lead.DMSSubscribed or $lead.DMSSubscribedDate and not both, right?
        Only the DateTime field.
        
        - Do I simply just replace all $lead.DMSSubscribed with $lead.DMSSubscribedDate in the code?
        Yes, that is, if you're going to convert a stringified DateTime (i.e., ISO8601 format) field into a Date, that's where you use the DateTime.
        
        However I don't think these are ISO8601 "yyyy-MM-dd'T'HH:mm:ss". They're actually ISO8601 "yyyy-MM-dd HH:mm:ss". That is, they have a space instead of the letter "T". So you can add this line to the code at the top:
        
        #set( $ISO8601WithSpace = "yyyy-MM-dd HH:mm:ss" )
        
        Then use $ISO8601WithSpace where you're using $ISO8601 now.
        
        Parsing a String to a Date requires that you tell Velocity (actually Java) all the parts of the format.
        
        - Do I uncheck the $lead.DMSSubscribed box in the Script Token?
        For clarity, yes, but it's harmless to leave it checked as you won't be using it. Leaving it unchecked means it will always have the value null. That may be more or less confusing if you accidentally use it, I don't know.
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Dec 3, 2019 9:33 AM
        Mark Correct
        Correct Answer
        Yes, that is, if you're going to convert a stringified DateTime (i.e., ISO8601 format) field into a Date, that's where you use the DateTime.
        I need to clarify. I actually meant - Do I simply just replace all $lead.DMSSubscribed with $lead.DMSSubscribedDateTime in the code? - NOT $lead.DMSSubscribedDate .
        
        Because the only field I will be using is the 'Product X DateTime' custom fields I converted the datatype from 'Date' to 'DateTime' on (i.e $lead.DMSSubscribedDateTime).
        
        Does that change anything from your previous reply?
        
        I also have a feeling all locations in the code below that says 'date' needs to change in some way as well as possibly deleting line 7 entirely. What do you see that is broken and needs to be changed?
        
        #set( $ISO8601WithSpace = "yyyy-MM-dd HH:mm:ss" ) #set( $defaultTimeZone = $date.getTimeZone().getTimeZone("America/Los_Angeles") ) #set( $defaultLocale = $date.getLocale() ) #set( $calNow = $date.getCalendar() ) #set( $ret = $calNow.setTimeZone($defaultTimeZone) ) #set( $calConst = $field.in($calNow) ) #set( $ISO8601DateOnly = "yyyy-MM-dd" ) ${display.list( $lead.entrySet(), "\u000a" )} #if( !$lead.DMSSubscribedDateTime.isEmpty() ) #set( $calDMSSubscribedDateTime = $convert.toCalendar( $convert.parseDate(     $lead.DMSSubscribedDateTime,     $ISO8601WithSpace,     $defaultLocale,     $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calDMSSubscribedDateTime).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Dec 3, 2019 9:46 AM
        Mark Correct
        Correct Answer
        You don't change any lines in the common header area. I see that you deleted a line, not sure why... all I said was to add the new line for the new ISO8601 format.
        
        The Velocity property names of the fields did not change when you changed the datatype; if you were to arbitrarily change the names in the code you'd just be pointing to null properties. You want to reference the current DateTime fields by their Velocity property names. Those are the names you see when you check the box in the tree and dump the entry set.
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Dec 3, 2019 10:24 AM
        Mark Correct
        Correct Answer
        Understood. You're right. I was thinking adding the "good" line and removing the "bad" line made sense BUT I should not be "thinking" as it is too dangerous. It is back to exactly as is with the new line added.
        The Velocity property names of the fields did not change when you changed the datatype; if you were to arbitrarily change the names in the code you'd just be pointing to null properties. You want to reference the current DateTime fields by their Velocity property names. Those are the names you see when you check the box in the tree and dump the entry set.
        After changing the datatypes I did, in fact, go back and rename the fields properly and therefore the proper Velocity names (Ex, DMS Subscribed DateTime) is reflected in the checkbox tree.
        
        I have corrected the common header area, replaced all $ISO8601 with $ISO8601WithSpace and all $lead.DMSSubscribed with $lead.DMSSubscribedDateTime.
        I have tested but it still reflects the same result - as I'm sure you're well aware it would.
        Next steps?
        #set( $ISO8601WithSpace = "yyyy-MM-dd HH:mm:ss" ) #set( $defaultTimeZone = $date.getTimeZone().getTimeZone("America/Los_Angeles") ) #set( $defaultLocale = $date.getLocale() ) #set( $calNow = $date.getCalendar() ) #set( $ret = $calNow.setTimeZone($defaultTimeZone) ) #set( $calConst = $field.in($calNow) ) #set( $ISO8601 = "yyyy-MM-dd'T'HH:mm:ss" ) #set( $ISO8601DateOnly = "yyyy-MM-dd" ) ${display.list( $lead.entrySet(), "\u000a" )} #if( !$lead.DMSSubscribedDateTime.isEmpty() ) #set( $calDMSSubscribedDateTime = $convert.toCalendar( $convert.parseDate( $lead.DMSSubscribedDateTime, $ISO8601WithSpace, $defaultLocale, $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calDMSSubscribedDateTime).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end
        Thank you so much. I cannot stress enough how grateful I am for your patience and help.
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Dec 3, 2019 10:30 AM
        Mark Correct
        Correct Answer
        I repeat, can you prove that the property names changed when you changed the friendly field names, or are you guessing?
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Dec 3, 2019 10:41 AM
        Mark Correct
        Correct Answer
        I'm sorry. I was wrong. I was not guessing intentionally - I can see the tree identifies the field as DMS Subscribed DateTime, however, rather than copying and pasting, this time I dragged that field into the script editor and it did read as $lead.DMSSubscribedDate.
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Sanford Whiteman on Dec 3, 2019 12:04 PM
        Mark Correct
        Correct Answer
        Not rushing you, in the event you intended to reply, rather just making it clear I cannot move forward without your help.
        
        Here is my preview-by-list test result...
        Like • Show 0 Likes0
        Actions
        Ronn Burner @ Ronn Burner on Dec 5, 2019 9:29 AM
        Mark Correct
        Correct Answer
        Sanford Whiteman Can you please help me make this work?
        I feel like the code below is precisely what you have advised me to do, however, since tests still display incorrectly as they have before. Obviously, I've done something wrong but I am unable to identify and correct it.
        Please and thank you.
        #set( $ISO8601WithSpace = "yyyy-MM-dd HH:mm:ss" ) #set( $defaultTimeZone = $date.getTimeZone().getTimeZone("America/Los_Angeles") ) #set( $defaultLocale = $date.getLocale() ) #set( $calNow = $date.getCalendar() ) #set( $ret = $calNow.setTimeZone($defaultTimeZone) ) #set( $calConst = $field.in($calNow) ) #set( $ISO8601 = "yyyy-MM-dd'T'HH:mm:ss" ) #set( $ISO8601DateOnly = "yyyy-MM-dd" ) ${display.list( $lead.entrySet(), "\u000a" )} #if( !$lead.dMSSubscribedDate.isEmpty() ) #set( $caldMSSubscribedDate = $convert.toCalendar( $convert.parseDate( $lead.dMSSubscribedDate, $ISO8601WithSpace, $defaultLocale, $defaultTimeZone ) ) ) #if( $date.difference($calNow,$caldMSSubscribedDate).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.cRMProSubscribedDate.isEmpty() ) #set( $calcRMProSubscribedDate = $convert.toCalendar( $convert.parseDate( $lead.cRMProSubscribedDate, $ISO8601WithSpace, $defaultLocale, $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calcRMProSubscribedDate).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.bHPHSubscribedDate.isEmpty() ) #set( $calbHPHSubscribedDate = $convert.toCalendar( $convert.parseDate( $lead.bHPHSubscribedDate, $ISO8601WithSpace, $defaultLocale, $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calbHPHSubscribedDate).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.autoCheckSubscribedDate.isEmpty() ) #set( $calautoCheckSubscribedDate = $convert.toCalendar( $convert.parseDate( $lead.autoCheckSubscribedDate, $ISO8601WithSpace, $defaultLocale, $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calautoCheckSubscribedDate).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.oAPSubscribedDate.isEmpty() ) #set( $caloAPSubscribedDate = $convert.toCalendar( $convert.parseDate( $lead.oAPSubscribedDate, $ISO8601WithSpace, $defaultLocale, $defaultTimeZone ) ) ) #if( $date.difference($calNow,$caloAPSubscribedDate).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.dealerWebsitesSubscribedDate.isEmpty() ) #set( $caldealerWebsitesSubscribedDate = $convert.toCalendar( $convert.parseDate( $lead.dealerWebsitesSubscribedDate, $ISO8601WithSpace, $defaultLocale, $defaultTimeZone ) ) ) #if( $date.difference($calNow,$caldealerWebsitesSubscribedDate).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.cRMSubscribedDate.isEmpty() ) #set( $calcRMSubscribedDate = $convert.toCalendar( $convert.parseDate( $lead.cRMSubscribedDate, $ISO8601WithSpace, $defaultLocale, $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calcRMSubscribedDate).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( !$lead.maxDigitalSubscribedDate.isEmpty() ) #set( $calmaxDigitalSubscribedDate = $convert.toCalendar( $convert.parseDate( $lead.maxDigitalSubscribedDate, $ISO8601WithSpace, $defaultLocale, $defaultTimeZone ) ) ) #if( $date.difference($calNow,$calmaxDigitalSubscribedDate).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end #if( $lead.dMSSubscribedDate.equals("") ) Your DMS Subscribed is false. #end #if( $lead.cRMProSubscribedDate.equals("") ) Your CRM Subscribed is false. #end #if( $lead.bHPHSubscribedDate.equals("") ) Your BHPH Subscribed is false. #end #if( $lead.autoCheckSubscribedDate.equals("") ) Your AutoCheck Subscribed is false. #end #if( $lead.oAPSubscribedDate.equals("") ) Your OAP Subscribed is false. #end #if( $lead.dealerWebsitesSubscribedDate.equals("") ) Your Dealer Websites Subscribed is false. #end #if( $lead.cRMSubscribedDate.equals("") ) Your CRM Pro Subscribed is false. #end #if( $lead.maxDigitalSubscribedDate.equals("") ) Your Max Digital Subscribed is false. #end
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Dec 5, 2019 11:13 AM
        Mark Correct
        Correct Answer
        You don't need to test all the code at once. Isolate a representative unit of code and test only that.
        
        This opening snippet, using the first field, works for me:
        
        #set( $ISO8601WithSpace = "yyyy-MM-dd HH:mm:ss" ) #set( $defaultTimeZone = $date.getTimeZone().getTimeZone("America/Los_Angeles") ) #set( $defaultLocale = $date.getLocale() ) #set( $calNow = $date.getCalendar() ) #set( $ret = $calNow.setTimeZone($defaultTimeZone) ) #set( $calConst = $field.in($calNow) ) #set( $ISO8601 = "yyyy-MM-dd'T'HH:mm:ss" ) #set( $ISO8601DateOnly = "yyyy-MM-dd" ) ${display.list( $lead.entrySet(), "\u000a" )} #if( !$lead.dMSSubscribedDate.isEmpty() ) #set( $caldMSSubscribedDate = $convert.toCalendar( $convert.parseDate( $lead.dMSSubscribedDate, $ISO8601WithSpace, $defaultLocale, $defaultTimeZone ) ) ) #if( $date.difference($calNow,$caldMSSubscribedDate).getHours() >= -24 ) You subscribed to Product X within the past 24 hours. #end #end
        
        If I set $lead.dMSSubscribedDate to 2019-12-05 03:00:00 (n.b. running this code at 2019-12-05T19:10:06Z, later on the same day) then I get the expected output:
        
        You subscribed to Product X within the past 24 hours.
        
        If I set $lead.dMSSubscribedDate to 2019-12-04 03:00:00 (one day earlier) then I get no output, also as expected.
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Dec 5, 2019 4:00 PM
        Mark Correct
        Correct Answer
        Thank you so much! That helped. So I tested meticulously, unit of code by unit of code, and then collectively a whole and in the preview-by-list mode it reflected all "true's" appropriately as well as all the "false's". That's a huge win as it clearly appears to be working perfectly.
        That said, when I run a smart campaign and actually send that same email - it's blank. So not exactly working perfectly. Does this make sense to you and/or what can I do from here?
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Dec 5, 2019 9:29 PM
        Mark Correct
        Correct Answer
        What about when you right-click someone in the Lead Database, choose Marketing » Send Email?
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Dec 6, 2019 10:43 AM
        Mark Correct
        Correct Answer
        That worked - and is the below image. Progress!
        
        Obviously, it can't display like this. I will play with this and test until I get to the desired result (2nd image below) but please let me know what you see clearly needs to be corrected and/or just any tips.
        
        Ideally, I'd like to have a sentence or two accompanied by an image as seen below for each unit of code (product section) which comes from my original unique emails. Can I just cut and add the HTML to the "You subscribed to DMS within the past 24 hours." section? Which should work but is that the way to do it?
        If you say, yes, am I crazy or does this mean this framework is 100% completed and ready to go?
        
        PRODUCT 01 = True
        PRODUCT 02 = False
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Dec 6, 2019 10:55 AM
        Mark Correct
        Correct Answer
        That worked - and is the below image. Progress!
        OK, that means your Smart Campaign wasn't in the right place in the MA hierarchy and didn't have the token available. Make sure the Program w/the SC can see the token (as is the case w/all tokens).
        
        Yes, you can add HTML where you currently have plain text. Velocity just outputs what you tell it to, it doesn't think about whether it has HTML tags or not.
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Ronn Burner @ Sanford Whiteman on Dec 6, 2019 11:20 AM
        Mark Correct
        Correct Answer
        OK, that means your Smart Campaign wasn't in the right place in the MA hierarchy and didn't have the token available. Make sure the Program w/the SC can see the token (as is the case w/all tokens).
        Oh my goodness. *slams face onto keyboard* You're absolutely right and such a rookie mistake! I obviously know that. I utilize dynamic tokens for utm parameters extensively throughout my dynamic programs. I cannot believe I didn't catch that. It's so obvious. Ugh! That was paralysis by analysis resulting from fear and pressure of trying to do VTL from a clean slate.
        Yes, you can add HTML where you currently have plain text. Velocity just outputs what you tell it to, it doesn't think about whether it has HTML tags or not.
        I just tested this is a couple spots and it rendered perfectly!
        
        Thank you, Sanford! Truly. This entire lesson was invaluable and I will take it and the code with me and utilize it as much as possible. This is high level and super cool stuff! I cannot thank you enough for your time, patience and help. You're my hero!
        1 person found this helpful
        Like • Show 0 Likes0
        Actions
        Sanford Whiteman @ Ronn Burner on Dec 6, 2019 12:19 PM
        Mark Correct
        Correct Answer
        Awesome, Ronn. Glad we were both able to persevere. Could you mark one of my answers as Correct? And also, if you don't already follow my blog, it's a good idea now that you're in the Velocity world.
        1 person found this helpful
        Like • Show 1 Like1
        Actions
Joke Van Essche Nov 15, 2019 2:42 AM
Mark Correct
Correct Answer
Ronn Burner Thanks for this topic!
Sanford Whiteman Is it possible to do the same with program membership instead of a boolean field? So: If Member Status = Registered in Program 1, then "welcome to session 1". If Member Status = Registered in Program 2, then "welcome to session 2".
Like • Show 1 Like1
Actions
- Sanford Whiteman @ Joke Van Essche on Nov 15, 2019 10:38 AM
  Mark Correct
  Correct Answer
  Unfortunately no. Program membership is not a direct property of the lead.
  
  If you used program membership to manage a segmentation, then the segment is a property of the lead (so could be used in personalization) but it's not updated in absolutely real-time.
  
  Or have a field on the lead that's used as a mirror for their program status.
  Like • Show 0 Likes0
  Actions