Extending User Security to a Field Level

Right now there is a relatively robust and easy way to establish roles that grant a user various levels of access to tables/views. However, there doesn’t appear to be a mechanism to get to field level validation. So what if the user role only givens them access to a filtered list of rows in any given table or view? How would you go about incorporating that into ASP.Net Maker? So let’s say you have a list of customer and a list of orders and a role for a customer service rep that only has access to orders created by a specific set of customers. How could you set that up using ASP.Net Maker)?

For design time settings, you can use the Field Visibility extension.For run time, you need to write your own codes to set the field visibility (e.g. in the Page_Load server event).if (condition) // Hide a field based on condition
Field.Visible = false;