We have been experiencing rows in our grid showing the wrong data. After extensive research, we have narrowed it down to the RecordContainerGenerationMode. When set to Recycle, and the grid is scrolled via code behind by 1 record, it sometimes shows the contents of the scrolled out record in the record that is scrolled into view. I used Snoop to look at the data bound to the UI. The data is correct for the row, but what is being present to the user is wrong. I changed the RecordContainerGenerationMode to LazyLoad and the condition goes away. However, scrolling becomes painfully slow. Is there anything we can do to ensure the proper data is shown to the user, while not affecting the performance of the scrolling?
Thanks
Dan
Hello Dan,
Thank you for your post. I have been looking into it and since this is not a known issue, I cannot be completely sure what can cause it, so could you please send an isolated sample project, where this is reproduced, so I can investigate it further for you.
Looking forward for your reply.
Stefan,
I’ll see if I can replicate it outside of our application.
Please take your time.
If you have any other questions with this matter, do not hesitate to contact us.
Danko/Stefan,
I’ve tried to replicate this outside of our application, but have not been able to. It happens so regularly within our application that it is becoming an issue to our customers. I noticed that you will have a presence at the Microsoft Build conference in a couple weeks. Is it possible that I can meet with somebody from Infragistics there to show them the issue so that we can try to get it resolved?
Could please try to reproduce this in a small sample since this could be vital for a further investigation, because most of our colleagues that will be on the conference are from our marketing team.
I am just checking if you got this worked out or you still require any assistance or clarification on the matter.
I have created a private case fro you (CAS-117238-F7Z1W6), where you can send me the sample.
I managed to come up with a test app that replicates the problem, but I’m having issues attaching it to my post. Perhaps it’s too big (8,500 KB). Is there another way I can get it to you?