Hello,
I have a template column in my XamGrid with a SumSummaryOperand that has the IsApplied property set to true.
My project uses MVVM and when the ItemsSource of the XamGrid is set to null, the IsApplied property of the SumSummaryOperand gets (undesireably) set to false. So, when the ItemsSource is set back to a collection, the summary is not displayed.
I put together a sample app to demonstrate. If you click the bind button, it runs a command that sets the ItemsSource to null, then to a new collection. The first time the button is clicked, you will see the summary. All subsequent times the button is clicked, the summary row will be blank.
If you comment out line 45 of TheViewModel.cs, then try the same test, you will see that the summary is never blank because IsApplied remains true.
Before running the app, please copy the following assemblies to the Libraries folder (they did not fit within the 200kb upload limit): InfragisticsSL4.v10.3.dll and InfragisticsSL4.Controls.Grids.XamGrid.v10.3.dll.
Does anyone know of a workaround for this issue? In the larger app that this issue affects, it is not as simple as ensuring that the ItemsSource is never set to null. One thought was to programmatically set IsApplied back to true whenever the ItemsSource changes, but there doesn't seem to be such an event to handle.
Thanks.
This is resolved in the latest service release for 11.1. You can download the service release from
https://es.infragistics.com/Membership/Default.aspx?panel=Downloads#Downloads
Please let me know if you have any questions.
Sincerely,ValerieDeveloper Support Engineer Infragisticswww.infragistics.com/support
I guess we can just let Infragistics support know that we are having the issue and hope they provide a fix.
Darrell,
Since upgrading to v2011.1 this same issue has returned. Can you reopen the case or open another one for me?
Please let me know how can I fix this issue.
I am using NetAdvantage 2011.1.
They fixed it with a special build which worked for me. The fix was then included in the 2011.1 build. However, since upgrading to that release, the fix is no longer working. :(
It looks like I will need to ask them to reopen the case.