One to many relationship, how to display/select

[Charles Carlin]

Given the following example what would be the best way to handle the given data in a single databound grid.

There are two main entities: users and hobbies. I would like a grid listing all users with some column in the grid displaying any hobby the user is interested in, where the user can select multiple entries. There are three data tables involved, a user, hobby and user_hobby_map table.

I was thinking some type of drop down grid or grid list with multi-select. But I can't seem to find the right combination. Any suggestions or hints as the best way to handle this using your grid control? Is there already a sample out there showing something like this that I could look at?

[Administrator]

Hi Chuck,

take a look at message http://www.syncfusion.com/forums/message.asp?MessageID=1313. Kai Iske has a multi-select combobox that you could use.

If, on the other side, you prefer to show each hobby in its own row and you want the table be grouped by user you should check out the DataBound\Hierarchical\ExpandGrid sample project.

Stefan

[socrates anibal rivera rivera]

Hello.

I have the same question.

The link you suggest is broken, can you correct it?

Thanks in advance,

Regards,

Socrates A Rivera R

[Dhanasekar Mohanraj]

Hi Socrates A Rivera R,

Please find the valid link here,

Forum link: https://www.syncfusion.com/forums/1313/currency-input-type-cell-type,

Please check this and revert us if you need further assistance for this.

Regards,
Dhanasekar M.

[sheh]

For a one-to-many relationship like users and hobbies, a common approach is to display users in the main grid and use a multi-select dropdown (such as a checked combo box) or a separate child grid to manage hobbies. The user_hobby_map table handles the many-to-many link, so the grid can bind users normally while loading selected hobbies into a multi-select column editor. This keeps the interface clean while allowing multiple hobby selections per user.

[Sweatha Bharathi]

Sheh,

Based on your query, we suggest using our SfDataGrid control, which supports managing relationships through the Master‑DetailsView. This feature allows you to represent hierarchical data in the form of nested tables. For example, you can display the username as the parent record and hobbies as the child records in a nested table.

Alternatively, you can use a GridComboBoxColumn to display a list of hobbies for each user, allowing users to select their desired hobbies from the available options. 

For your reference, we have provided the User Guide and feature links. Kindly review them and let us know if you have any questions. We are happy to assist you.

UG Link: DataGrid documentation

Feature tour link: DataGrid feature tour