Difference between revisions of "Long Date Format"

From AgileApps Support Wiki
imported>Aeric
 
imported>Aeric
 
Line 9: Line 9:
<someDate>1228457520000</someDate>
<someDate>1228457520000</someDate>
</syntaxhighlight>
</syntaxhighlight>
<!-- pre V7, not sure if this is relevant
;Considerations:
*If Date Format is defined from ''Date Format Settings'' in [[Personalize]] or from ''Date & Currency Format'' in [[Company Information]], then date formats used in data policies may produce an error message
If User Date format/Company Date format is set, setting hardcoded default date values for custom date/datetime fields, formula fields or wherever date values are used for ex: data policies etc, may give an error "Date should be in User/company’s Date Format -dd-MM-yyyy or DateTime formatdd-MM-yyyy hh:mm [AM/PM]".
In short, hardcoded date values should not be set if User Date format/Company Date format values are set.
-->

Latest revision as of 19:54, 14 January 2013

Resources in APIs that apply Date or DateTime values use a Long Date Format, which is different from theMM-DD-YYYY date patterns described in the UI.

Long Date Format is based on the Java class Date, which is defined as the number of milliseconds since January 1, 1970, 00:00:00 GMT.

This Long Date Format encodes dates and times as a number, which can then be applied to complex filters and formulas in the AgileApps Cloud platform.

Example
<syntaxhighlight lang="xml" enclose="div">

<someDate>1228457520000</someDate> </syntaxhighlight>