Hi,
We upgraded our infragistic a month ago from 8.2 to 9.1. However, we see some strange issue when we group by. Duplicate rows occurs when we tried to group by : See the pics below:
Wrong display with two group of rows: (using infragistic 9.1). We can even see a seperator for these two groups of rows as shown below.
Correct display with just one group of rows: (using infragistic 8.2)
Is there any changes you can think of course such error? We are using bindingList(bindingList) to build the band -> sub band structure of the grid.
Many Thanks,
Xin
Hi Xin,
There have not been any changes to GroupBy functionality that I am aware of - except for bug fixes.
Are you using the latest service release? How to get the latest service release - Infragistics Community
Hi Mike,
Yes, I am using latest version of Infragsitic 9.1. If I changed version back to 8.2, everything works as expected. But when using 9.1, duplicate rows appears.
Is there any change related to data binding or sibling band? I saw something like sibling band changes in 9.1. Is this a known bug in 9.1.x version?
Thanks,
In that case, I recommend that you see if you can duplicate this in a small sample project and submit the issue to Infragistics Developer Support. If it still happens with the latest service release, then it's clearly a bug.
Hi, just wanted to add a bit more details pls use file attached to this post
We finally got some time to look into the issue. It looks like the band count is not updating on the in the same way as before. We created a sample application that mimics the grouping logic in our production code.The sample app allows a user to add or remove N generations from a tree like structure that binds to the grid. The changes to the structure are propogated via ListChangedEvents.On the right of the main UltraGrid there is a Band count history (most recent first) that updates on every PropertyDescriptor ListChanged event. The solution includes 2 projects, both point to the same source files. The only difference is a refferences to infragistics versions.
To reproduce the issue:1)Add 5 generations2)Remove 5 generations
InfragisticsTest82 project (v8.2)after step 1: the log history reads 1 2 3 4 5 6after step 2: the log history reads 1 2 3 4 5 6 6 5 4 3 2 1this means that bands were propertly removed and at the end number of bands was 1.InfragisticsTest91 project (v9.1)after step 1: the log history reads 1 2 3 4 5 6after step 2: the log history reads 5 6 6 6 6 6 6 5 4 3 2 1 this means that bands were not propertly removed and at the end number of bands is still 5. Looks like only one band is getting removed at the very end.
So we think that something had changed in the way change in property descriptors is communicated to the grid. Could you please help us with this issue?Thank YouMikhailPS Looks like edit post functionality is not working properly
Hi,We finally got time to look into the issue and it looks like the band count does not get updated properly. The same exact code works fine in 8.2. I have a sample application that demonstrates the discrepancy in DisplayLayout.Band count(attached) I was not able to get the exact behavior with sibling bands, However I suspect that two are related. Please advise. Thank you