DataPager: New Row added when commiting edit in Paged RadGridView bound to QCV(AsNoTracking Source)
Posted on:21 Oct 2016 10:35
Posted on:21 Oct 2016 08:25
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?
Posted on:21 Oct 2016 08:11
Any news guys?
Posted on:20 Oct 2016 19:14
It looks like it works only without any include usages try to use some include and it won't be working.
Posted on:20 Oct 2016 18:15
I've downloaded Telerik_UI_for_WPF_2016_3_1017_Dev_Hotfix.zip Bug still happens, how did you test it?
Posted on:20 Oct 2016 17:44
deleted by artem.oschepkov
Posted on:14 Oct 2016 12:08
Yes, you can test it with the upcoming internal build - next Monday.
Posted on:14 Oct 2016 10:23
Have you fixed that?
Posted on:14 Oct 2016 10:23
What does it mean guys it's got completed?
Posted on:11 Oct 2016 11:50
And how long will it take to get a fix for us?
Posted on:11 Oct 2016 07:02
Hello, we use our own save scenario we don't need attached objects at all, that's why we use for showing in the grid as no tracking. Still waiting for resolution.
Posted on:05 Oct 2016 11:36
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.
Posted on:27 Sep 2016 12:34
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.
Posted on:23 Sep 2016 18:46
Hi guys. Ignoring the problem won't make it go away. We pay good money for using your product and expect that amateur bugs such as this one gets fixed asap. Why would you want to have a product with this ugly bug? 3 months and no-one has fixed this yet? Really??? Give us the source code and we could fix it in 1 hour. Don't worry, we wont charge you, we just want the bug fixed. Aren't you ashamed? I am so freakin surprized by your inability to act in this matter that i am considering leaving Telerik and building our own stuff. It is a BUG!! Just FIX it!!!!
Posted on:23 Sep 2016 08:26
Hello guys, we really need this fix, and we really expected to see it in the last release. Could you find a way to fix it asap.
Posted on:23 Sep 2016 08:13
Posted on:29 Aug 2016 12:12
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.