This article explains the mapping of date time fields. Byteline provides a powerful way of configuring date time by typing the various supported formats.
You can specify the date using an expression that refers to a date output from another node or from the flow input. Byteline automatically determines the date time format and parses it to generate the format required by the integration.
Parsing by function
parseDatefunctions should only be used when automatic date parsing doesn't work.
This function can be used to parse the date time from the flow input data or the output data of a node. Learn More.
If you don't want to get a date from an expression, it can be specified using the below formats.
Below are several formats of date time supported by Byteline. You can copy and paste the format and then change it according to your needs. The time part optionally supports
PM along with the timezone (in the three-letter form, e.g., PST).
tomorrow at 9PM
next Friday at 7PM
2/13/2022 8PM EST.This is an example of the U.S. date (MM/dd/yyyy) format along with the timezone.
2020-10-26T16:56. If the timezone is not provided, the default account timezone is used.
1393462573. Unix-based time, aka epoch. Both seconds and milliseconds e.g.
1393462573000version is supported
The date can be typed directly into the text field as shown in the below example:
You can also configure the date time relative to the current time. You can either add or subtract months (
mo), weeks (
w), days (
d), hours (
h), and/or minutes (
m). This format must start with
- . Below tokens can be used. You can combine multiple tokens, as shown in the examples section.
+1mo -> 1 month from now.
-3w -> 3 weeks before now.
+3h30m -> 3 hours 30 minutes from now
+3d -> 3 days from now.
The relative dates can be directly typed into the text field as shown below.
You can use the below function to specify the dates.
now: This function can be used to output the current time in the format your need. Learn More.