CODEWITHSUNDEEP
sharepointconnectionweb-parts
Ali
Ali

Reputation: 595

connecting web parts in sharepoint

I am trying to connect to simple webparts in my sharepoint team site, i need one of the webparts to filter its information based on what it recieves from another webpart

I am using the query string filter webpart and the a list view webpart but no matter how i connect them always i am getting this error

"Web Part Error: This page has exceeded its data fetch limit for connected Web Parts. Try disconnecting one or more Web Parts to correct the problem."

What should I do and what am I doing wrong

update: i can connect to web parts on some other pgae, but getting this error on the DispForm.aspx page of a certain item , is webpart connections not allowed there ??!!

Upvotes: 1

Views: 11978

Answers (4)

Marees
Marees

Reputation: 11

I have fixed this issue.

Problem

In the sharepoint list, filtered column name in query strng fitlter has been deleted and added new column with same name.

Solution: Remove filter and Set current view again in webpart properties. It works fine.

With Regards, Marees

Upvotes: 1

user4531
user4531

Reputation: 2575

The page 'DispForm.aspx' usually is a form of a SharePoint list and different rules apply to list-form pages than on pages that do not belong to a Sharepoint list (and the differences are hardly documented). I solved the problem by workarounds; you could use not a ListViewWebPart, but a DataViewWebPart (Using Query String and Data view WebPart), or you could avoid the QueryStringFilterWebPart by using URL parameters that the ListViewWebPart understands (ListViewWebPart Filter Param).

Upvotes: 0

mindzhang
mindzhang

Reputation:

Me too,you look this url http://blogs.msdn.com/sharepointdesigner/archive/2008/03/26/sharepoint-conference-building-a-sharepoint-designer-mashup-part-1.aspx

Upvotes: 1

Jim Fiorato
Jim Fiorato

Reputation: 4872

There is an issue with creating QueryString filter webparts in sharepoint, when you're not using the Web UI (I'm making an assumption that you aren't).

This fella here has a post about it and how he hacked around the issue.

http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/0328f1b2-20cd-427f-887a-e2925bd695e3/

Another option is not using the QueryString filter web part at all, and just passing querystrings to a regular web part.

http://mo.notono.us/2008/04/moss-filter-views-through-url-query.html

Upvotes: 4

Related Questions