We have confirmed the issue that you have reported. Unfortunately, it turns out that there is not easy fix for it and we will have to re-work our internal data engine considerably in order to resolve this issue.
Here you can follow its status.
There is a workaround possible. Create a local field that will store and cache the last reported current item by reading it from DataView.CurrentItem. Then each time that you receive the CurrentChanged event compare the current value of DataView.CurrentItem with the old cached value. If they are different then you really have the current item being changed.
Please, excuse us for the inconvenience. We will do our best to resolve this issue as soon as possible.
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>