Timezone binding issue to Workflow Form with hosted feature layer data
I have an issue with 5 hours being added to my local datetime when I use the context variable to retrieve an existing value from a table in a hosted feature service. The use case is an attribute editing form for related tables in the hosted feature service.
My VertiGIS Studio Windows Server timezone settings:
Publish my hosted feature service with these timezone settings:
Mobile app Region settings:
Confirm in Item Manager:
In Go app, add a related record with my local time:
ArcGIS Online hosted feature table shows in local time:
Related record edit form in ArcGIS Online Map Viewer shows the expected local time:
Related record in Go app Feature Details (popup) shows local time:
Click Edit Record and it pulls up with +5 hours:
It seems like the problem is caused at the Workflow level, since the local time displays everywhere else, except in my edit form. And the edit form is adding the five hours to my local time, as if Workflow thinks it needs to be in UTC. (?)
-
Offizieller Kommentar
Note for future readers - Alex submitted a support ticket, and we filed this behaviour as a bug (242950 - Display form does not properly display date time values obtained from Workflow context inputs).
As a workaround you can either manually adjust the time value to be correct, or use a Format Date activity in your workflow to process the context input, and pass the Unix time output to the Set From Element activity for the Date Time Picker in the Display Form.
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
1 Kommentar