Discussions

Ask a Question
Back to all

ConcurrencyId increment behavior

Hello,

We sometimes get several versions of the same work order and its Equipment Worked On items within a fixed time window (the same day), and we need to keep only the latest one.

Is ConcurrencyId the right field to use for deduplicating work order records? When a record is saved, does its ConcurrencyId go up by 1 (its own counter), or does it take the next number from a counter shared across all records? Can it ever go down or reset, for example after a delete and re-add or a data migration?