This is no longer an issue. Upgrading to 9.1 fixed this bud.
To expand on your example, if there is a table with the columns 'UserName' and 'Favorite_Color'. The 'Favorite_Color' column has a bound parameter linked to it. The bound parameter would provide a list of options to the user, e.g. blue, green, yellow.
These values are independent of what is currently stored in the table rows.
When the user queries the table, and decides to change the 'Favorite_Color' value for multiple users, updating this field in row 1 to be blue, and then updating the field in row 2 to be green the table would save the updated data from both rows. If the user updates the field in row 1 to be blue, and the field in row 2 to be blue, then the table is only saving the update to the first row. When the same value from the linked parameter is used while trying to update multiple rows, the updates are not captured, and the user is having to update and save the table 1 row at a time.
