Hello,
we have a new Request to Pin and Move Grouped Columns:
When we now move "Grinding machine..." so the complete group should be moved and not just the HeaderColumn.
Is that Posssible?
Hello CSchmitt,
The answer to your question is yes. An entire FieldGroup (all of it's Fields and Header) can be moved by default among the rest of the Fields/FieldGroups whether it is fixed (pinned) or not.
I have atttached a sample application, that uses the approach from above.
If you have any questions, please let me know.
Thanks for your Quick Answer.
I looked at the Project but I can't get it worked with 15.2.
It always says:
Error 2 The name "FieldGroup" does not exist in the namespace "http://infragistics.com/DataPresenter". C:\Users\j5sx1h\Desktop\XamDataGrid_sample\XamDataGrid_sample\MainWindow.xaml 18 6 XamDataGrid_sample
Error 3 The tag 'FieldGroup' does not exist in XML namespace 'http://infragistics.com/DataPresenter'. Line 18 Position 7. C:\Users\j5sx1h\Desktop\XamDataGrid_sample\XamDataGrid_sample\MainWindow.xaml 18 7 XamDataGrid_sample
Error 1 The type 'dataPresenter:FieldGroup' was not found. Verify that you are not missing an assembly reference and that all referenced assemblies have been built. C:\Users\j5sx1h\Desktop\XamDataGrid_sample\XamDataGrid_sample\MainWindow.xaml 18 7 XamDataGrid_sample
So not sure whats the problem.
The FieldGroup class (along with all of it's functionalities) is a part of the Field Grouping feature in our XamDataGrid, which is not available in the WPF 15.2 product version.
Presuming that the field grouping functionality you have introduced in your application (the one on the screenshot) is a custom one by retemplating certain elements, then the field moving for an entire group should be manually implemented as well.
For a direct and practical overview of the Field Grouping feature, you can take a look at the "xamDataGrid > Organization > Field Grouping" sample from our WPF Samples Browser for 16.2.
Thank you for the feedback.
If you require any further assistance on the matter, please let me know.
Thank you again for your Answer. We have to Discuss if we can Upgrade to 16.2 or if we have to reimplement this function.