How do I preserve the original StatusCurrent value in StatusBefore using ExecuteUpdate in Entity Framework?

This behavior happens because the update expressions in ExecuteUpdateAsync are evaluated as part of one SQL UPDATE statement, so any expression that references a column that is also being updated can end up using the “new” value instead of the original value. In your case, when you write:

CSHARPCopied
.SetProperty(b => b.StatusBefore, b => b.StatusCurrent)
.SetProperty(b => b.StatusCurrent, (int)newStatus)

both setters are part of a single UPDATE. The expression for StatusBefore ends up seeing the effect of the update to StatusCurrent, so instead of preserving the original value (2) you get the new one (3).

Workarounds

1. Raw SQL Command
   You can avoid this issue by executing a raw SQL UPDATE where you control the order of evaluation. For example:

   CSHARPCopied
   var ids = string.Join(",", bookingIds);
   string sql = $@"
       UPDATE Bookings
       SET StatusBefore = StatusCurrent,
           StatusCurrent = {newStatus}
       WHERE BookingId IN ({ids})";
   var updatedRows = await _dbContext.Database.ExecuteSqlRawAsync(sql);

   This way, you’re certain that the SQL engine reads the original value of StatusCurrent for the assignment to StatusBefore.

2. Two-step Update
   Another approach is to update the records in two steps. First, store the original value (or copy it into a temporary field if you have one), and then update the current status. For example:

   CSHARPCopied
   // First update: copy StatusCurrent to StatusBefore.
   await _dbContext.Bookings
       .Where(b => bookingIds.Contains(b.BookingId))
       .ExecuteUpdateAsync(s => s
           .SetProperty(b => b.StatusBefore, b => b.StatusCurrent));
   
   // Second update: update StatusCurrent to the new status.
   await _dbContext.Bookings
       .Where(b => bookingIds.Contains(b.BookingId))
       .ExecuteUpdateAsync(s => s
           .SetProperty(b => b.StatusCurrent, _ => (int)newStatus));

   This guarantees that StatusBefore gets the original StatusCurrent before it is overwritten.

Summary

The key point is that when multiple property updates are performed in a single ExecuteUpdateAsync call, the assignments are not processed sequentially in a way that guarantees one will see the “old” value from the database. When an update expression refers to a column that is also updated in the same statement, the order of evaluation may lead to unexpected results. Using a raw SQL command or splitting the update into two operations can provide the control you need to preserve the original value.