EditDate update frequency when editing is performed

[MarcMuehleisen]

Hello everyone,

We are currently implementing Field Maps Tasks in a workflow to log maintenance work. As part of this process, we frequently edit features to provide the necessary information for each task. For data quality reasons, we need to ensure that the time of the last edit is correctly stored in the EditDate field.

When checking via REST, we noticed that this field does not update if multiple edits are made to the same feature within the same minute (e.g., from 14:55:01 to 14:55:59). These multiple edits are of course saved each in between. EditDate only updates once the next minute begins and the editing has started.

We have specifically applied an EditDate calculation using the expression now() both in the form and in tasks (e.g., when pressing the Start Task button for automatic updates). I’m aware of the warning message stating “Field contains a calculated expression in the Form”, but our intention was to ensure the calculation runs when a Action is performed.

My question:
Is this behavior related to Field Maps, or is it inherent to how the EditDate field works? Does anyone have insights or a workaround for this?

Thanks in advance!

[ChristopherCounsell]

It sounds like you have manually created an EditDate field.

Enabling editor tracking should create 4 fields that are system managed. You should not be able or trying to calculate these fields in Field Maps. They will store the date and time the edit was submitted by the user.

If you manually create this field, it's just another field, until you update it yourself using calculations or manual updates.