Hello,
I have an uncatchable fatal exception when sometimes I was trying to apply a Filter to a XamPivotGrid, the message was "The given key was not found in the dictionary". I have attached the stack trace in the attachement, can you urgently look into this? Thank you!
Regards
Hello pebg,
Thank you for your post.
I would like to investigate into this issue that you are reporting with the XamPivotGrid, but unfortunately, the attached .zip file is empty. Would it be possible for you to please provide an attachment that contains the stack trace of the exception that you are seeing?
Please let me know if you have any other questions or concerns on this matter.
Sincerely,AndrewAssociate Developer
Hi Andrew,
Sorry for the mistake, I have attached the stack trace, thank you very much Andrew, this is an fatal fail that's very important for the project, please let me know if you need any more informations.
Thank you for the attached stack trace.
After stepping through the source code of the XamPivotGrid, it appears that this stack trace is pretty standard for creation of filters on the control. One thing that I did notice is that the FlatDataModelProvider class has had quite a few changes made to it in the past, and this leads me to wonder which specific version of Infragistics WPF 2015.1 that you are using? While I can't seem to find a work item in our internal tracking systems that matches this exception trace, it is certainly possible that this was fixed if you are using an early version of 2015.1.
Another thing that I feel could possibly be a partial cause to this is the issue related to the discussion that we are currently having on another forum thread - again about XamPivotGrid filters. For reference, that forum thread is here: http://www.infragistics.com/community/forums/t/108158.aspx. Are you saving and loading customizations prior to setting up your filters in the XamPivotGrid in order to reproduce this exception, or is this something that can be reproduced simply by setting a filter in the XamPivotGrid on your end?
Yeah exactly, we save the customization before setting the ItemsSource, and LoadCustomization after setting the ItemsSoruce. Here's the code for the refresh of FlatDataSource:
public void RefreshDataSource(IEnumerable<T> dataSourceItems) { var layout = this.SaveCustomizations(); ItemsSource = dataSourceItems; this.LoadCustomizations(layout); }
Mee too I thought that maybe it's the LoadCustomization applying too soon and the whole ItemsSource is not yet rendered, so I also have tried a Dispatcher with low priority to the LoadCustomization, but it changes nothing. I will provide you a sample soon for you to reproduce this issue. And as for the updates, which version should I take to no longer have this problem? I confirm that the dll for the FlatDataSource I use is "InfragisticsWPF4.Olap.FlatData.v15.1", "InfragisticsWPF4.Olap.v15.1". Thank you very much Andrew.
More information on the version:
InfragisticsWPF4.Olap.FlatData.v15.1 File Version : 15.1.20151.2156
InfragisticsWPF4.Olap.v15.1 File Version : 15.1.20151.2156
If you confirm that this problem is already fixed in a later version, please let me know which one to download and where we can find it. As for the license I think it's not a problem.
Thank you very much