Format Date feature - Unix timestamp not valid

(Andrew Catchpole) #1

Any suggestions on whether the Unix timestamp is a valid input to Format Date or not?

Date/Time
1580067000000
Format
DD-MMM-YY HH:mm:ss

Error “Date/Time is not a valid input”

(Andrew Catchpole) #2

Reference to Flowxo help…

Format Date

In this action, you’ll give in your own date/time to the first input, and then tell Flow XO what you’d like the output to look like in the second input.

You’ll be given a select box that gives you various options for formatting your given date - but if you’re an advanced user you can use the pencil icon to edit the select box and enter your own format. There’s a full reference for all possible formats here.

Let’s look at our example date 04/22/2027 12:47:32 and our special input Now as an example.

Giving 04/22/2027 12:47:32 in the first input and dddd, MMMM DD, YYYY [at] hh:mm:ss A will give us the output Thursday, April 22, 2027 at 12:47:32 PM.

That’s a really complex format request! Fortunately, it was selected directly from the select box. A simpler example would be, using our special Flow XO Date/Time input Now , passing the format dddd in the second input.

That would give us the simple output Thursday (Which is of course the Now in respect on when this article is being written - it’s a Thursday today!)

As a final note - you might combine the output here with the Text (String) or Number services to work with the outputs you generate and really fine tune your outputs.

(Nathan Stults) #3

I do not believe that a unix timestamp is a valid date input, however you could use a code block to convert a unix timestamp to a date object.

(Andrew Catchpole) #4

@nathan
I suspect that you are correct however the Flowxo help implies that all possible formats may support Unix time. There’s a full reference for all possible formats here.

It woul dbe good to know for sure

Plus unfortunately I dont think that I will have the right skills to writing a “code block” unless someone has got some examples?

Regards Andrew

Token Output
Month M 1 2 … 11 12
Mo 1st 2nd … 11th 12th
MM 01 02 … 11 12
MMM Jan Feb … Nov Dec
MMMM January February … November December
Quarter Q 1 2 3 4
Qo 1st 2nd 3rd 4th
Day of Month D 1 2 … 30 31
Do 1st 2nd … 30th 31st
DD 01 02 … 30 31
Day of Year DDD 1 2 … 364 365
DDDo 1st 2nd … 364th 365th
DDDD 001 002 … 364 365
Day of Week d 0 1 … 5 6
do 0th 1st … 5th 6th
dd Su Mo … Fr Sa
ddd Sun Mon … Fri Sat
dddd Sunday Monday … Friday Saturday
Day of Week (Locale) e 0 1 … 5 6
Day of Week (ISO) E 1 2 … 6 7
Week of Year w 1 2 … 52 53
wo 1st 2nd … 52nd 53rd
ww 01 02 … 52 53
Week of Year (ISO) W 1 2 … 52 53
Wo 1st 2nd … 52nd 53rd
WW 01 02 … 52 53
Year YY 70 71 … 29 30
YYYY 1970 1971 … 2029 2030
Y 1970 1971 … 9999 +10000 +10001
Note: This complies with the ISO 8601 standard for dates past the year 9999
Week Year gg 70 71 … 29 30
gggg 1970 1971 … 2029 2030
Week Year (ISO) GG 70 71 … 29 30
GGGG 1970 1971 … 2029 2030
AM/PM A AM PM
a am pm
Hour H 0 1 … 22 23
HH 00 01 … 22 23
h 1 2 … 11 12
hh 01 02 … 11 12
k 1 2 … 23 24
kk 01 02 … 23 24
Minute m 0 1 … 58 59
mm 00 01 … 58 59
Second s 0 1 … 58 59
ss 00 01 … 58 59
Fractional Second S 0 1 … 8 9
SS 00 01 … 98 99
SSS 000 001 … 998 999
SSSS … SSSSSSSSS 000[0…] 001[0…] … 998[0…] 999[0…]
Time Zone z or zz EST CST … MST PST
Note: as of 1.6.0 , the z/zz format tokens have been deprecated from plain moment objects. Read more about it here. However, they do work if you are using a specific time zone with the moment-timezone addon.
Z -07:00 -06:00 … +06:00 +07:00
ZZ -0700 -0600 … +0600 +0700
Unix Timestamp X 1360013296
Unix Millisecond Timestamp x 1360013296123

(Nathan Stults) #5

You can format a timestamp into a Unix Timestamp using X or x as the doc suggests, but a unix timestamp is not a recognizable format that Flow XO can read using the DateTime task. Here is a sample that uses a code block to convert a unix timestamp into a datetime:

Nathan

(Andrew Catchpole) #6

@nathan
Your suggested code is simple and brilliant. This code does everything I need. Thank you!!!

(Nathan Stults) #7

Great, glad to hear it is working for you!