Can you, please, open a support ticket and send us a runnable sample where the described problem can be reproduced, so we can examine it and assist you further?

Yes, you can test it with the upcoming internal build - next Monday.

Hello guys,

the investigation of this case showed that the issue comes from the fact that the source collection doesn't track any changes to its entities. This is because of the usage of the AsNoTracking extension method.

Generally, using the AsNoTracking method is recommended when you don't want to save the entities back to the database (i.e. in read-only scenarios). It is important to be mentioned that using the method is not recommended when you intend to update the entity as this will mean that Entity Framework has no way of knowing that it needs to save your changes back to the database. 

That being said, the scenario is not common, as in such mode, the grid should be used as read-only, hence, it is not top priority for us. Still, we will work on its resolution in future, but keep in mind that any changes you made will not be persisted.

As to the last comment about the source code, note that all of our clients have access to our source code in the accounts.

Hello all,

The bug is planned to be reviewed for the upcoming Service Pack. We are prioritizing all our bugs and, unfortunately, we have directed our efforts on other issues with higher priority in the past release. Hopefully, we will have some progress for the Service Pack.

Hello Artem,

Excuse me for the delay. The bug is with status approved but we cannot provide you with an exact time frame when it will be revised at our end. I have increased its priority so that we consider it as soon as possible.