Hello All,
while I am aware of the hierarchical features of the xamDataGrid, my question relates to the idea of showing overflowing columns of a data row by expanding it, so that the user does not need a horizontal scroll bar. The number of columns is fixed, so I can clearly decide which rows are seen in the "overview", and which should go into "details".
However, it seems that this is not possible at all for the xamDataGrid. The idea also could be to have a self-referencing field somehow spit out by the view model, by having a getter that returns essentially a "this" pointer, but it is somehow strange to me.
Any ideas on that?
BR Florian
Hello Florian,
Thank you for choosing Infragistics.
Would you please provide me with more detailed information in regards to the Layout of the XamDataGrid you would like to achieve? By saying "Flat DataSource" are you saying that you would like to keep the DataSource initially empty or something else? In order not to use a horizontal ScrollBar, how would you like to visualize each Field for every Record? Having this information would help me further investigate this matter for you.
Looking forward to hearing from you.
Tacho,
thanks for you answer. What I like to do is the following:
The datagrid shows all columns from the primary field layout as usual in a row.
The row has a + sign at the beginning to expand the view
User clicks on + will trigger to expand the row to show columns which are listed in an additional auxiliary field layout
As I understand the documents the expansion will only work with master/detail relationships. The "flat" means that I do not have master/detail entities in the background but only one entity type.
But I still would love to hide some columns and only display them on request, in order to save space.
Thanks and BR Florian
Hello,
Thank you for your feedback. I am glad to know that I was able help you achieve the functionality you were looking for. I believe this thread can help other people looking for a similar solution.
If you require any further assistance on this matter, please do not hesitate to ask.
thanks I came up with a similar idea. I think it's ok for what we need, however, as a suggestion for the future you could pass on to your guys that nested field layouts could be used also without actually changing the datasource.
Thanks Florian
Thank you for your feedback.
I have been looking into your issue and I have prepared a sample application for you to test if the desired behavior is achieved.
An approach I can suggest you is to use a helper class that contains the details of your main DataItem. Inside the Product class I have created an ObservableCollection of ProductDetails instances. In order to achieve your behavior you will probably need only one instance of the ProductDetails class inside the Details collection. This way you should be able to access easily each property and still keep the FieldLayouts functionality.
Would you please take a look at the sample I have attached and if your issue is still reproduced or this is not the behavior you were aiming for, would you please modify the sample according to your behavior and send it back to me? Having this information would help me in my further investigation of your issue.