Expand button for master-detail grid not working properly

[Roger Criebaum]

I have a grid (ItemsDataGrid) that shows data based on a couple search criteria. The grid columns are fixed. The data provided is hierarchical: the DataSource is a List<TItem>; the TItem class has a member SubstituteItems of List<TItem>. I have two sets of data: (1) The main List<TItem> and (2) a list of ALL substitute items. I have created a GridViewDefinition with a grid (subItemsGrid) and a DataSource of the full list of substitute items, and added it to the Items.DetailsViewDefinitions. The TItem class has three specific members: ITEM_VEND_NO, ITEM_NO and PARENT_ITEM_NO. Items that have substitute items will have the PARENT_ITEM_NO set and the list of substitute items added to the member list.

The app as two basic modes: (1) show items only for the vendor selected; (2) show all items for a specific vendor type (many vendors). When showing records for a single vendor, the master-details expand button works with no issue. However, when viewing multiple vendors' items (grouped by vendor), some rows that have detail records do not expand.

I'm sure I have either set something or not set something that's causing this. I can't find any examples of what I'm doing online. Could this be because I'm using the same class type for the details grid?

Any assistance is greatly appreciated.

K

Attachment: SkyForecast_264eafe8.zip

[Mohanram Anbukkarasu]

Hi Kevin, 

Thanks for contacting Syncfusion support.  

We are little unclear with your scenario. We suspect that you are unable to expand the details view when DataGrid id grouped by a column. We have prepared a simple sample using the provided details and it is available in the following link for your reference.  

Sample link : https://www.syncfusion.com/downloads/support/forum/159029/ze/SfDataGrid_DetailsView1198747718  

Please have a look at this sample and try to reproduce the reported issue in it and revert to us with the modified sample with the replication procedure and video illustration of the reported issue. It will be more helpful for us to find the exact cause for the issue and to provide a prompt solution at earlier.  

Regards, 

Mohanram A.