You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 19, 2023. It is now read-only.
Include functionality to translate string or numerical formatted fields for time to ISO 8601 standards.
For example a year field with the format of 1986.00 with data type as double, the user would enter the format key of YYYY.00 to produce the ISO 8601 value of 1986-01-01T00:00:00Z.
Example use cases:
US vs European conventions on month and day order MM-DD-YYYY vs DD-MM-YYYY.
Time fields that are typed as numerical or string data types to the data type expected by importer.
Non-Standard date formats such as 9/20/23:30 to become 2020-09-01T23:30:00Z if defined by the key MM/YY/hh:mm
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Include functionality to translate string or numerical formatted fields for time to ISO 8601 standards.
For example a
year
field with the format of1986.00
with data type as double, the user would enter the format key ofYYYY.00
to produce the ISO 8601 value of1986-01-01T00:00:00Z
.Example use cases:
MM-DD-YYYY
vsDD-MM-YYYY
.9/20/23:30
to become2020-09-01T23:30:00Z
if defined by the keyMM/YY/hh:mm
The text was updated successfully, but these errors were encountered: