I suggest you ...

Don't use Page.InitComplete in QueryableFilterRepeater and DynamicFilter controls

ASP.NET Dynamic Data QueryableFilterRepeter and DynamicFilter controls currently use Page.InitComplete logic to dynamically generate their content. This prevents you from re-using these controls on a custom filter template to generate filters for a related (parent or child) table. By the time the custom filter template is initialized the Page.InitComplete has already fired and the controls simply don't work.

3 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    amanekamanek shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for all the feedback on this item. Please be advised that we have moved this item to the ASP.NET User Voice site (http://aspnet.uservoice.com) and transferred the associated votes. We are going to close this item out and release your votes back to you so you can apply them elsewhere. Note that the votes will remain with the item on the other site, so the item will not lose any of its current vote count, and you will recoup your votes on this site. To track the status, post comments, or add votes on this item, please go to http://aspnet.uservoice.com/forums/41202-asp-net-webforms/suggestions/3090790-don-t-use-page-initcomplete-in-queryablefilterrepe and sign in using your current user ID and login.

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base