Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
220
Best Practices: UltraGrid Paging, Sorting, AJAX, WebParts & Connections & SharePoint
posted

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

I'm using the UltraWebGrid in SharePoint, in a set of 3 WebParts. The idea for this implementation is as  follows:

  • #1 ... retrieves data from a service, displayed in the grid (WebParts 2&3 show no data)
    • When the user selects a row in #1, the rowID is passed (via connection framework) to ...
  • #2 ... which queries the service, passing the ID providing to it from #1, and displays the result in the grid.
    • When user selects a row in #2, the rowID is passed to ...
  • #3 ... which queries the service again, passing the ID provided from #2, displaying the result in the grid.


My questions:

  • Does the grid require myGrid.EnableViewState = true; ?
  • The WebPart connections framework allows me to pass data to/from my web parts .. but the order in which these connections are fired can't be guaranteed. (ie - #3 might happen before #2, etc) The only guarantee I have is that during or after OnPreRender(), the property values will be reliable. -- How will this affect my usage of the grid?
  • Is InitializeDataSource() the only place I should be invoking these?
         myGrid.DataSource = [datasource];
         myGrid.DataBind();
  • One setting in the web part is a PageSize, so that users can configure the size of the pages displayed in the grid. I've had mixed results with the effectiveness of this setting (myGrid.DisplayLayout.Pager.PageSize), depending on when in the code it is set. (Before/After Databinding, etc). When should this value be set?
  • Given that the grid re-binds itself after a Paging operation, will the Active/Selected Row persist or will I have to maintain this manually in the ViewState? (I have the same concern regarding filtering/sorting.)

 

I've already looked at the pomegranate solution, but its architecture is drastically different than our implementation. I've also looked through this but as for these topics, that doesn't shed much light.

I submitted an official dev-support ticket, but I've since noticed our subscription has ended.

 

 

Thanks!

Joe Brockhaus

  • 220
    posted

    no longer using infragistics grid for this project because it simply doesn't work the way it should and answers don't come easily, if at all. :)

     

    I'd still love to get answers to the above questions, if possible.