Change Data Value based on Datetime | Community
Skip to main content
A
Anonymous
October 9, 2016
Solved

Change Data Value based on Datetime

  • October 9, 2016
  • 1 reply
  • 3225 views

Hi there,

I am trying to populate a custom field with a variable depending on the datetime in a field we have synced from Salesforce. Depending on the date of the Salesforce field, I want the custom field to populate with a specific string, these are different depending on the week.

For some reason this flow step is not working as I would suspect and I think it is due to the datetime field not reading as between these dates. The flow step I have set up is as follows:

The choices follow on as this so that each lead within each week increment gets a new value. The Segmentation Datetime field also reverts to having "12:00" at the end which I don't want (as I just want leads within these 2 dates inclusive) - I am not sure if this is the cause of my problems.

During testing I could not get the flow to work with separate dates and all leads reverted to choice 1. Does anyone have any ideas?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

Yep, the fact that "pod time" is CDT is exactly the reason that almost everyone whose instance time (or, let's say, "corporate HQ time") is not also CDT has potentially broken tokens. I got into that problem a lot in some of my recent posts about Dates and Times in Velocity, but it exists outside of email scripting, too.

Anyway, yes, as long as you calibrate to CDT, you want ranges like yyyy-MM-dd 00:00 - yyyy-MM-dd 23:59. 

1 reply

SanfordWhiteman
SanfordWhiteman
New Participant
October 9, 2016

Datetimes always have times -- if you don't want times, use Date fields (although there are still implicit timezone, and thus time, concerns, they're out of your hands).

Ending at "2016-10-16 12:00" is going to lop off all the matches after 12:00 on 2016-10-16, which isn't what you want, as it's not inclusive of the entire day(s).

If every lead you're running through the flow is matching Choice 1 (which isn't really "reverting," since it's not the default) then I would suspect there's something up with the data that's actually being pushed to Segmentation Datetime.  Can you add {{Lead.Segmentation Datetime}} to an email and post a screenshot of the results for a known lead?

A
Anonymous
October 9, 2016

Thanks Sanford.

The data coming through the field is datetime so presumably I could have 10/10/2016 00:00 to 16/10/2016 23:59? I basically want the increments from Monday to Sunday.

Although I have just added {{lead.Segementation Datetime}} to an email on one of our known leads and I got CDT time:

This may explain why I was having issues as CDT is still Sunday 9th October.

We can determine the weekly increments based on any timezone we choose (as long as it's consistent) but to do this how would I set up the flow step?

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
October 9, 2016

Yep, the fact that "pod time" is CDT is exactly the reason that almost everyone whose instance time (or, let's say, "corporate HQ time") is not also CDT has potentially broken tokens. I got into that problem a lot in some of my recent posts about Dates and Times in Velocity, but it exists outside of email scripting, too.

Anyway, yes, as long as you calibrate to CDT, you want ranges like yyyy-MM-dd 00:00 - yyyy-MM-dd 23:59. 

Terms & ConditionsAccessibility statement

Loading footer...