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
The default type is string which results in ODK collect filling in just the date portion of the timestamp. With the value set to dateTime, the timestamp is filled correctly.
Note: if we want to fix this in pyxform, it would be wise to add a way to
over-ride the type of a calculation rather than fix it directly for this
one use case (which seems weird).
For example, we could allow people to specify the type of a calculation in
the type column. Instead of putting just calculate there (whose type would
default to string), they could do calculate dateTime there, or calculate
integer there, or what have they. There is already precedent for this in
the language, with select_one CHOICE_LIST being specified, which creates a
specific kind of select_one, or with select_one choice_list OR_OTHER.
The default type is string which results in ODK collect filling in just
the date portion of the timestamp. With the value set to dateTime, the
timestamp is filled correctly.
vs
Reply to this email directly or view it on GitHubhttps://github.com//issues/115
.
The default type is
string
which results in ODK collect filling in just the date portion of the timestamp. With the value set todateTime
, the timestamp is filled correctly.vs
The text was updated successfully, but these errors were encountered: