Has anybody else encountered an issue with displaying a dynamic date/time value in a text widget causing an unwanted conversion to happen? The data is in a Referenced Feature Service living in Alaska Standard Time, and the timestamp matches in the table everywhere, including map viewer, SDE and EB. Alaska Time is also set as the 'preferred' time zone on the Feature Service.
I am trying to display the most recent time value in the text box using a Max(date) query. It does display the correct value but applies an unneeded/incorrect shift to an unknown time zone (not UTC). For example, 4pm is being changed to 8am on the same day. A -8 hour shift is being applied *only* in the text widget. The Table widget for the same service and field displays the correct time, as does the map Pop-up and Feature Info widgets.
I have tried changing the time settings away from 'Device' in the project settings. Even locking the whole project to the correct time zone doesn't do anything.
What am I missing, or have I found a bug that needs to be logged?
We are using Experience Builder native to Portal 11.3.
