nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Specify Time Zone option for Editor Tracking

RobertO_Donnell

Since we can not use 'database time' for Editor Tracking in web services, there should be an option to set the Time Zone instead of, o in addition to, a generic UTC for editor tracking.

Encuentra más publicaciones etiquetadas con

Status: Abrir

Comentarios

Anonymous User

100% agree with previous posts --- Just to make the simple DB setting change to use UTC time, I have to update every 'Creation' and 'Modification' date captured to match UTC time. Otherwise I'll have DB times mixed with times being recorded with UTC...not ideal for those that have queries using these dates. This is no small task and it is quite time consuming - even with a script doing the work.

All of the update work could have been avoided if I could have had the option to choose UTC and a time zone.

TrevorHart1

Or at least make the error "00129: <value> Editor Tracking dates in database time zone" a warning only.

I 100% understand Esris' rationale but in many cases users only work in one time zone and its standard to record date/time in local database time and not UTC.

Únete a la Conversación

Inicia sesión para publicar, seguir contenido y más. ¿Nuevo aquí? Regístrate gratis.