Power Platform Community Forum Thread Details

SQL Server provides a row versioning mechanism using rowversion (or timestamp) columns.

Add a rowversion column to your SQL table:
```
 
```
sql

ALTER TABLE YourTable ADD RowVersionColumn ROWVERSION;
- This column auto-updates every time a row is modified.
Retrieve the row version when loading data into your Canvas app:
- When a user selects a record, store the rowversion value.
Check row version before updating:
- When submitting updates, compare the stored rowversion with the current rowversion in SQL.
- If they match, allow the update.
- If they don’t match, inform the user that the data has changed.
Modify the SQL Update Query:
```
 
```
sql

UPDATE YourTable SET Column1 = @NewValue, Column2 = @NewValue2 WHERE ID = @RecordID AND RowVersionColumn = @StoredRowVersion;
Check affected rows:
- If rows affected = 0, another user has already modified it.
- Show a message to reload the latest data.

If data integrity is highly critical, you can implement record locking:

🔥 Downside: Can cause records to remain locked if a user forgets to save.

If using Power Automate or SQL Patch, add an extra check before updating:

✅ Use Row Versioning (rowversion) for reliable optimistic concurrency.
✅ Use Locks (LockedBy) if you want pessimistic concurrency.
✅ Use timestamps (LastModified) if you don’t need strict control.