3 Answers, 1 is accepted
0
Hello Jeff,
It depends on your definition for a lookup edit control. Just to see if we are on the same page, I am thinking about a control that displays a value (content) in its normal state, and a combo box, bound to the lookup data in the edited state. The underlying value would typically be an ID that would have to be mapped to a user-friendly representation.
At the moment we are planning on providing a lookup column for the RadGridView control, but we have not thought about shipping a separate control. What is your usage scenario? Maybe that can change our plans.
Best wishes,
Hristo Deshev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
It depends on your definition for a lookup edit control. Just to see if we are on the same page, I am thinking about a control that displays a value (content) in its normal state, and a combo box, bound to the lookup data in the edited state. The underlying value would typically be an ID that would have to be mapped to a user-friendly representation.
At the moment we are planning on providing a lookup column for the RadGridView control, but we have not thought about shipping a separate control. What is your usage scenario? Maybe that can change our plans.
Best wishes,
Hristo Deshev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Jeff
Top achievements
Rank 1
Rank 1
answered on 13 Jan 2009, 01:44 PM
Hello Hristo,
Yes, we are talking about the same thing. The display value is a user friendly string and the stored value is an ID from a lookup table.
This control has 2 common use cases:
1) within a grid. we typically only show enough columns to fill the display area in a grid
2) within a data entry form. for entities with a significant number of properties, it is better to provide a data entry form (using loose controls) than force the users to do all editing within a grid. we also have alot of deep relationships in our model, and for certain entities they are best represented with a form rather than a grid.
We are building a large enterprise app, and we make use of both scenario's. It would be fantastic if you could provide both in time for your Q1 release.
Thanks alot for your quick response!!
Jeff
Yes, we are talking about the same thing. The display value is a user friendly string and the stored value is an ID from a lookup table.
This control has 2 common use cases:
1) within a grid. we typically only show enough columns to fill the display area in a grid
2) within a data entry form. for entities with a significant number of properties, it is better to provide a data entry form (using loose controls) than force the users to do all editing within a grid. we also have alot of deep relationships in our model, and for certain entities they are best represented with a form rather than a grid.
We are building a large enterprise app, and we make use of both scenario's. It would be fantastic if you could provide both in time for your Q1 release.
Thanks alot for your quick response!!
Jeff
0
Accepted
Hi Jeff,
The lookup column is definitely on our list for Q1. We'll see how that goes with providing it as a standalone control.
Best wishes,
Hristo Deshev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
The lookup column is definitely on our list for Q1. We'll see how that goes with providing it as a standalone control.
Best wishes,
Hristo Deshev
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.