locked
Is there a maximum number of connections between two webparts? RRS feed

  • Question

  • Hello all,

    Is there a maximum number of connections one can have between two webparts in SP2007?

    I have two webparts on a webpart page:

    1.       Webpart A: List view webpart displaying data dictionary entries  grouped by category, approx 100 items paged by groups of 7 categories.

    2.       Webpart B: Data view webpart displaying data dictionary entries and associated detail, paged in groups of 1 item. Source of data view webpart is a linked data source that combines two lists.

    I have a webpart connection set up between Webpart A and Webpart B, with Webpart A providing the data dictionary entry parameter to Webpart B.

    The connection works beautifully when the list for Webpart A is around the 50 item mark. However, when I increase it to 100 items (in the future, the list will likely have 500 + items), the connection stops working for a good percentage of the connections. In other words, when the list for Webpart A has 100+ items, and I click a radio button on Webpart A, Webpart B will often not filter, even though there is an associated value.

    The same thing happened to me with a completely different set of webparts on a completely different site collection.

    I apologize in advance if this question has been answered elsewhere. I have spent a good amount of time browsing the forum looking for an answer, but I certainly could have missed something. It seems there are questions about the max number of webparts one can connect, but not the max number of connections between two webparts.

    Thank you very much for your help with my question. Please let me know if I can provide any additional information.

    Tuesday, January 18, 2011 5:38 PM

All replies

  • You are only describing a single connection between the web parts so connecting A to B creates a single filter connection.  For that reason I don't believe that to be your problem.  I think the configuration of the web parts at the time the connection was established might be the problem.

    You created the connection and then modified the source web part.  It is quite possible that the connection took a snapshot of the source properties and is using that and not seeing the updated configuration.

    1. Delete the web part connection between A and B.
    2. Configure A for the future value you expect to use.
    3. Recreate the connection between A and B.
    4. Test

    That should do it!

     


    I trust that answers your question...

    Thanks
    C

    http://www.cjvandyk.com/blog
    Monday, January 24, 2011 9:43 PM
    Answerer
  • Hi Cornelius,

    Thank you so much for your help! Unfortunately, I'm still running into the same issue, even after I delete and recreate the connection. However, maybe I'm understanding this part incorrectly:

    1. Configure A for the future value you expect to use.

    I took this to mean making sure my webpart settings were established prior to reconnecting the webpart (and not making any changes to the setting after the connection had been set). Is this correct?

     

    Thanks again!!

     

    Wednesday, January 26, 2011 6:58 PM