Bug
After publishing a joined feature class with a table containing date fields, the time zone advanced parameter is not respected for the feature class in a server service.
| Bug ID Number | BUG-000104985 |
|---|---|
| Submitted | May 8, 2017 |
| Last Modified | August 17, 2025 |
| Applies to | ArcGIS GIS Server |
| Version found | 10.4 |
| Operating System | Windows OS |
| Operating System Version | 2012 |
| Version Fixed | 10.6.1 |
| Status | Fixed |
Workaround
1. Create static data from the dynamic table by using the Join tool to append the desired fields to the feature class.2. If using a single database i. Create a relationship class with a one to one relationship between the feature class and table. ii. Publish the related data (in advanced parameters use Pacific Standard Time or the local time zone in the time properties), and configure the popups in the web viewer to display features from the related table.3. If using two separate databases i. Create a dblink in the sde database to the database containing the table. ii. Create a view directly in the sde database to pull data from the external database into sde. iii. Create a relationship class using the new view in the same database as the feature class. iv. Publish the related data (in advanced parameters use Pacific Standard Time or the local time zone in the time properties), and configure the popups in the web viewer to display features from the related table.4. Add a time component to that date field, and append '12:00' to existing non-null date entries. i. If entering a date without a time component, add 12 hours to the date - instead of entering '5/27/2014', enter '5/27/2014 12:00PM' or '5/27/2014 12:00'. This offsets the UTC time.Steps to Reproduce
Bug ID: BUG-000104985
Software:
- ArcGIS GIS Server
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App