topic Re: Time field in Pop-up in ArcGIS Web AppBuilder Questions

Time field in Pop-up

LianaSmith — Wed, 20 Apr 2016 12:55:33 GMT

I have a layer with a data that updates every 15 minutes. In my Web Map and Web Application the time field shows time that is 4 hours earlier than the time that I see in Arc Map (So it shows it in a different time zone).

How can I use the same time zone that I have in Arc Map?

I do not need Time Animation.

Re: Time field in Pop-up

BrianCarson2 — Wed, 20 Apr 2016 15:08:18 GMT

This is caused by the date field being converted to an Epoch when it is uploaded to ArcGIS Online. From the documentation, the date and time in a pop-up do not match the date and time in the underlying data. Servers store dates in Coordinated Universal Time (UTC). Web browsers convert the date to local time. For example, if you look at a time field in a pop-up and you are located in California during standard daylight time, what you see is 8 hours earlier (UTC-8) than the time in the data. This offset might affect the date as well. If you look at a pop-up with data from 7/7/2011 12:00 a.m., you see 7/6/2011 5:00 p.m. To have the same date shown in ArcGIS Online as in ArcMap, we would need to run the Convert Time Zone geoprocessing tool.

Re: Time field in Pop-up

LianaSmith — Wed, 20 Apr 2016 15:47:29 GMT

Hi Brian,

Thanks for your response. When I run the Convert Time Zone tool I get an Error Executing Function. My layer has a joint table, could be the reason in that? In MXD I see my local Miami time. In a Web Map I see 4 hours behind

Re: Time field in Pop-up

BrianCarson2 — Wed, 20 Apr 2016 15:50:17 GMT

The joined table shouldn't cause an issue. When in ArcMap, if you go to Geoprocessing > Results > Expand the current session, what is the error message? The time difference between the MXD and the web map is due to the way that the server stores dates and times.

Re: Time field in Pop-up

LianaSmith — Wed, 20 Apr 2016 18:06:04 GMT

I changed the parameters as below:

I get this error:

Re: Time field in Pop-up

BrianCarson2 — Wed, 20 Apr 2016 19:21:45 GMT

Hey Liana,

Try exporting the table after you make the join. That should allow you to run the Convert Time Zone tool without error.

-Brian

Re: Time field in Pop-up

LianaSmith — Wed, 20 Apr 2016 19:32:04 GMT

Brian,

Did you mean export the layer? If I export it, it does not get updated. Because my layer is in file geodatabase and the joint table is coming from SQL Server

Re: Time field in Pop-up

BrianCarson2 — Thu, 21 Apr 2016 13:06:09 GMT

Liana,

I did mean export the layer. The error is caused by running the tool on a feature class with a joined table. I tested this in a File Geodatabase on my end, and received the same error as you did above. However, if I export the join, I no longer receive the error.

- Brian

Re: Time field in Pop-up

LianaSmith — Thu, 21 Apr 2016 14:01:01 GMT

Thanks Brian, but I cannot export the join because the table is in SQL database in which I don't' have writing access. And in my understanding, if I export the join table to my file geodatabase, it won't be updated.

Re: Time field in Pop-up

BrianCarson2 — Thu, 21 Apr 2016 14:21:34 GMT

Hello Liana,

With the data being in an enterprise database that we do not have write access to, there may not be a way around the error. You could always open a support case with our Geodata team to see if they have any ideas as to how we could make it work. Unfortunately, I'm not terribly familiar with the enterprise database side of things.

-Brian

Re: Time field in Pop-up

LianaSmith — Thu, 21 Apr 2016 14:37:13 GMT

Thank you anyway for your help!!!

Re: Time field in Pop-up

AbiDhakal — Fri, 20 Sep 2019 16:24:47 GMT

Hey Brian,

I'm late in the show, but I'm in the show now nonetheless.

I'm having issue with date on the web appbuilder application versus the GIS Server date.

The date field for the feature service in the web appbuilder is not matching with the date field for the same feature layer for the same field on the Server. Pretty much what you are referring to in your message above.

I do not have the advantage of create a new field and running the time zone conversion geoprocessing tool. My data is directly being fed to another system once I copy the layer from the Server. So, I can only copy the erroneous layer.

A day in the data is making a lot of difference. Especially, for a new fiscal year date. I'm trying to put in 10/1/2018 for the start of a new fiscal year in the feature service in my web appbuilder, but the data on the Server is showing up as 9/30/2018, and for this reason any data that is being generated on 10/1/2018 is not being included in the current fiscal year. Has this problem been resolved? What is the workaround?

Thank you for your help.

Abi