Exporting with multiple Raddocks

2 posts, 0 answers
  1. Ivy
    Ivy avatar
    5 posts
    Member since:
    Jun 2013

    Posted 20 Nov 2013 Link to this post

    I have a RadDockZone with multiple Raddocks.  Each Raddock contains a multi-page RadGrid with an Export to Excel button inside the CommandItemTemplate.  Lets say I have 3 Raddocks, raddock1 being at the very top of RadDockZone.  When I try to export the bottom 2, the radgrid is expanded and all records are displayed.  It removes the paging and does not export.

    If I only have one raddock inside the raddockzone, it exports the radgrid just fine.

    anyone ever ran into the same issue?
  2. Slav
    Admin
    Slav avatar
    1356 posts

    Posted 25 Nov 2013 Link to this post

    Hello Ivy,

    I tried to reproduce the problem you described, but to no avail. You can find attached the sample page that I used for testing. Please compare it to your actual project and check if there are differences in the setup (you will need a Northwind database attached to run it). I would also suggest examining this screen capture of the behavior on my end in order to let me know if I am missing something.

    If you are creating the docks with their content programmatically, I would recommend doing so on the PreInit or Init event of the page, as shown in the online demo My Portal. This way you will ensure that the docks and the grids inside are initialized properly.

    Note that currently I am guessing what your setup is. If you are still having difficulties, please try modifying the attached sample in order to recreate your scenario or if this is not possible, send a simple, fully runnable project that isolates the problem so that I can inspect it locally and provide a more to the point answer.

    Regards,
    Slav
    Telerik
    If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed now.
  3. UI for ASP.NET Ajax is Ready for VS 2017
Back to Top