Introduction
In multi-user applications, one of the biggest challenges is preventing data conflicts. What happens if two users edit the same record at the same time? Who wins? Which data should be saved?
To solve this problem, Power Apps relies on a powerful mechanism called Entity Tag (ETag). Although developers rarely see it directly, ETag plays a critical role in maintaining data accuracy and consistency.
This article explains ETag in Power Apps from concept to implementation, with practical relevance for real-world projects.
What is an Entity Tag (ETag)?
An Entity Tag (ETag) is a unique version identifier attached to a record in a data source. It represents the current state of that record. Whenever a record is updated, its ETag changes automatically.
In simple terms:
ETag is a version stamp that tells Power Apps whether a record has changed since it was last read.
Why ETag is Important in Power Apps
Power Apps is often used in enterprise environments where:
Multiple users access the same data
Data is edited simultaneously
High data accuracy is required
ETag ensures
No accidental overwrites
Safe multi-user editing
Data consistency
Reliable conflict detection
It supports Optimistic Concurrency Control, assuming conflicts are rare but verifying before saving.
How ETag Works in Power Apps
Behind the Scenes Flow
User opens a record
Power Apps fetches:Record data
Associated ETag (version)
User edits data
Another user modifies the same record → ETag changes
Original user tries to save → Power Apps compares stored ETag with current ETag
If they don’t match → Power Apps blocks the update and raises a conflict.
ETag & Concurrency Control
Power Apps uses Optimistic Concurrency by default:
| Step | Action |
|---|---|
| Read | Record + ETag captured |
| Modify | User changes data |
| Save | ETag compared |
| Mismatch | Save fails |
This protects your system from silent data loss.
Data Sources That Use ETag
ETag is actively used in:
Join the conversation! Your thoughts help the community grow.