We're using a Xamdatagrid and storing our customization XML in a database for persistence. We have "AllowFixing" set to "Near" on our xamdatagrid.FieldSettings. When a user pins a column, the column is moved to the front, as expected, the pin widget appears pinned, and the appropriate separator bar appears between the pinned column and all of the other columns.
When the user restarts the application and reloads their data, however, the pin widget appears unpinned and the separator bar is gone. The underlying customization XML is intact and contains a FixedLocation="FixedToNearEdge" attribute. The column itself remains in the pinned location on the grid, it is simply no longer pinned. What additional steps do we need to take to make sure we can persist pinned columns? How do we set the pin widget to "pinned"?
Hello Nat,
I followed the steps you suggested and was unable to reproduce the behavior you're describing for LoadCustomization and fixed fields in XamDataGrid. I have attached the sample project I used to test this. Please test this project on your PC; whether or not it works correctly may help indicate the nature of this problem.
If the project does not work correctly, then the change in behavior is due to differences in your environment from mine and these differences can be anything from operating system version to the specific version of the Infragistics DLL versions used. My test was performed using version 16.2.20162.1006 and 16.2.20162.2141 in WPF product.
Please provide more details about your machine and version of the assemblies that you are referencing so that I can modify the environment that I am testing in to match yours. If the project does show the product feature working correctly, then more information will be needed to reproduce the issue in a sample that can be used for debugging. It will help if you can provide a small, isolated sample application that demonstrates the behavior you are seeing. This can be done by either making the sample that I provided more like your application or by isolating the behavior from your application by removing dependencies on any third parties or databases.
Please let me know if I can provide any further assistance.
Sincerely,ZhivkoAssociate Software Developer
Much appreciated! I'll take a look at this solution this morning.
A cursory investigation reveals that my organization appears to be on Infragistics 12.2. We're building against the latest .NET framework. This issue is present on all of our machines, which run a wide range of specifications, from low end to high end. Both Windows 7 and Windows 10.
Thank you for your feedback.
Since version 12.2 is no longer supported(please see the Product Lifecycle page) the best I can suggest is to download and test your application with the latest Service Release of version 16.2.
If you are able to reproduce the same issue for FixedFields with version 16.2, the best for us would be to provide a small isolated sample(or modify our project) and send back to us, this way we will can run and use for debugging locally. If you are unable, able to provide an isolated sample we may be able to give suggestions if you provide the code that you are using.
Let me know if you have any questions.
Hello Nad,
I just want to add a suggestion to test your sample application with the latest Service Release of 12.2, just in case if it has been an issue that is fixed in the latest Service Release.
Thank you for your help, Zhivko. I'll take this higher up my management chain to see if we can update our licenses to the latest supported version.
Cheers,
Nat
Thank you for your feedback. Let me know if you need any further assistance.