I have a bogus error in the designer, apparently, when using the xamGrid 14.1.
"A column has been added with an Empty key. All columns must have a unique key."
The same thing happens in the sample browser: IGGrid.Samples.Data.HierarchicalData
The error appears on the first column in the first child band/relationship. That column has a key.
Any advice? Its not a biggie since the code compiles and runs correctly. Its not annoying enough that I'd move the junk to the code behind. I'm a bit of a WPF novice. Are there error suppression options to tell the WPF designer not to complain about certain issues?
Thanks, David
Hello David,
I have reproduced this specifically and exclusively in the Visual Studio 2013 IDE. I was not able to reproduce it in Visual Studio 2010 or 2012. Being that this is unexpected behavior, I have asked our engineering staff to examine this further. To ensure it will receive attention, I have logged it in our internal tracking system with a development ID of 190872. I've also created a private case for you so that you can track the progress of this issue. This case has an ID of CAS-152988-Z4Z9V2 and you can access it at http://es.infragistics.com/my-account/support-activity.
Please let me know if you have any other questions or concerns on this matter.
Sincerely,AndrewAssociate DeveloperInfragistics Inc.www.infragistics.com/support
Any update for this issue? I do not have access to the case number referenced above.
Hello Gary,
Development issue 190872 was fixed a couple of service releases ago for our WPF product. This was fixed in versions 14.1, 14.2, and 15.1. The specific versions that this issue was fixed in were 14.1.20141.2283, 14.2.20142.2178, and 15.1.20151.2008. You can download the service release under your account on our website by selecting the "Dev Tools" tab, selecting the volume you are using, and then selecting the "Service Releases" tab. These tabs can be found here: https://es.infragistics.com/my-account/keys-and-downloads.
OK, I am on WPF v14.2.20142.2024, so that explains why I still see this error. Thanks!
As a side note, I worked around this issue a little in my current version by doing something like this:
<ig:ColumnLayout Key="Details" AutoGenerateColumns="True" />