You are viewing limited content. For full access, please sign in.

Question

Question

Seconds dropped from value of conditional decision conditions

asked on August 17, 2018 Show version history

Use Case: I have 2 "date time" values (ie "8/17/2018 2:08:30 PM") that I am comparing against each other in a conditional decision to determine if entry 1 was modified before or after entry 2. I am utilizing the "LastModifiedDate" property for each entry that is returned from a search activity.

I am able to consistently replicate that the "seconds" from the 2nd value is always dropped. I have even created tokens, set the properties to "date time" and replicated this instead of using the LastModifiedDate property directly. This yields the same result. 

After several hours of troubleshooting, I was able to determine this was why my workflow was not working properly and determine a workaround. If I format the token in the second comparison field manually by specifying the formatting in token dialog, it works as expected. The question is, why do I have to manually format the value for this to work? The data for the seconds is obviously retained, since when it is manually formatted, it shows the correct number of seconds for the entry in question. 

I have attached screenshots to demonstrate the details. I also opened a support ticket, just so the issue was logged.

Many thanks for your time, 

Jason

This Does Not Work (Tokens).JPG
This Does Not Work.JPG
This Works (Detail).JPG
This Works (Tokens).JPG
This Works.JPG
This Works.JPG (46.21 KB)
0 0

Answer

SELECTED ANSWER
replied on August 20, 2018

Hi Jason,

This is a known issue in Workflow. You'll see in the release notes

The Time token does not record seconds. (75630)

The workaround is what you're currently doing, by applying token formatting. This has also been communicated in the support case you opened for this same question.

Regards

0 0
replied on August 20, 2018

Many Thanks Alex!  I will be sure to check the release notes first next time :)

0 0
replied on March 14, 2019

Hi Alex,

I wasn't able to get this nifty work-around to work. I'll keep trying but do you know if this issue in the backlog?

-Ben

0 0
replied on March 14, 2019

Where was the time value coming from in your case?

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.