I want to have a clean code-behind that uses binding to populate the list values and the selected index in the dropdown lists in both the MasterTableView and the Edit Form's FormTemplate.

I can make it work without adding the strings and integer fields to the ViewModel, but the code behind is extensive and messy.  I can't figure out any clean way to do it.  

I looked at the GridDropDownColumn control, but found that it's supposed only to have datatables underlying it (http://www.telerik.com/community/forums/aspnet/grid/populating-griddropdowncolumn-from-code-behind.aspx), and only found examples of it being bound to a source whose connection string etc. were declared in the .aspx (not in the code behind).  I'm retrieving my values via Entity Framework and then a subsequent manipulation to acquire the values for the correct language, so that doesn't work for me.

I can't declaratively specify the options for the dropdown list in the .aspx due to the need to translate them, but if I don't declare them in the XAML, then I can't bind the selected value, because it finds that the corresponding list item doesn't exist.  I also can't even bind the selected value in the case of the MasterTableView's view mode entry because of the need to translate the text to be displayed using a function that's called server side.

As-is, in ItemDataBound, for EACH dropdown field in my form, there's code to:

1. Populate dropdown values list manually in Edit Form (requires casting the bound item, getting the list of values with translations, and manually creating ListItems
2. Setting selected item in Edit Form (reading the value from the underlying data source item and using .FindControl to get the control that I need to update)
3. Setting default value for the dropdown list in the Insert form
4. Set value for the field in the MasterTableView (again doing the translation)