Hi Paul, thanks for your reply, which in isolation, does make sense. They key part of your point is the assumption that the Value part of the row source dataset is not unique. This is possible, but rare, and even in that case, it would be logical to return any or 1st of corresponding values.
The real issue here though I would argue is that when you present a control, you almost always want to prepopulate it existing (data bound) values. Every data form works like this. You support SelectedValuePath and DisplayMemberPath, which is great, and usually standard functionality. All your users are going to have to implement extra lookup code to either populate SfComboBox.Text, or generate another item model to populate SelectedItem, rather than the normal practice of just setting the SelectedValue.
I suggest it would be better to implement as most do, and just display 1st or any of corresponding values, in which case you will cover the 90% usage scenario, which is that the rowsouce is a unique dataset.
Thanks,
Phil