title: How do you handle reporting filters in ASP.NET MVC?
body: <p>For a given report, the user will want to have multiple filtering options. This isn't bad when the options are enumerations, and other 'static' data types, however things can get silly fast when you need a select list that is populated by fields stored in a table in the backend. </p>
  
  <p>How do you handle this scenario?  I find myself constantly reshaping the View data to accommodate the additional filter fields, but it really is starting to be a bit much tracking not only the selected options, but also the options themselves...</p>
  
  <p>is there not a better way?</p>