05-06-2014 09:41 PM - edited 05-06-2014 09:44 PM
Previous to the Core 02 update when setting a decimal property on an entity that had a precision that is out more than 4 decimal places, that value was rounded by the framework to the appropriate 4 decimal places. This way, when saved to the database, the entity framework and the DB values match.
Since the update, the framework no longer rounds the values, so when you try to perform a subsequent update, the value in the DB is compared to the value in the entity in the generated SQL where clause. This results in an "Row was updated or deleted by another transaction" error.
This is a show stopper for us, since we have hundreds of calculations that will regularly go out past 4 decimal places if not rounding.
Anyone else encountered this problem yet?