Remove Editor Tracking Time-zone Restriction

Idea created by mlou on Aug 15, 2016
    Reviewed
    Score70
    • rex.m
    • mlou
    • anne_shanahan
    • charmalees
    • henry296
    • ryanuthoff
    • kericks

    When publishing a feature class with Editor Tracking enabled to a Feature Service we are forced to use UTC zone because sometimes editors can be in a different time-zone.  Many users though never have users in other time zones, or even aren't concerned about where their editors are, but would like to track edits in local or database time.

     

    Please allow feature services to use editor tracking in database time and not force UTC.  Many queries are based on local/database time, and having to convert these queries into UTC is unnecessary overhead.

     

    If anything, the Error that occurs when editor tracking is enabled in local/database time should at most be a Warning to the user that they can then choose to ignore or fix.