Hot answers tagged connected-web-parts
5
saving session state varibles can be done using:
public string Name
{
get
{
return Page.Session["SaveName"] as string;
}
set
{
Page.Session["SaveName"] = value;
}
}
this is a getter/setter to save/get from session state
to use this do the following:
this gets the value ...
4
Cross-Page connections are only supported by a few old webparts as it became obsolete after SharePoint 2003.
In order to support Cross-Page connection the web part need to:
derive from the Microsoft.SharePoint.WebPartPages.WebPart instead of System.Web.UI.WebControls.WebParts.WebPart (the recommended approach since WSS2.0/MOSS2007)
declare the interface ...
2
The major difference in these approaches is that in the second approach the interfaces listed here http://msdn.microsoft.com/en-us/library/ms469765%28office.14%29.aspx are specific to SharePoint so these would only work when you are developing SharePoint web parts but the first example is generic and is SharePoint independent.
In scenarios where you just ...
2
To accomplish that, you'd need to have some code that dynamically sends a query string prameter over to the newform page of the Notes list. The newform page would have some code on it that parses the query string and sets the desired drop down list value depending on who the user is.
Typically those associations have to be built, SharePoint doesn't do ...
2
This error simply means that the web part being edited does not support connections - it has not been coded correctly.
In this case I was receiving the error because I placed the ConnectionProvider and ConnectionConsumer attributes and methods on the UserControl objects inside the Web Parts, rather than the Web Parts themselves.
2
If the Web Part that is being connected to is on another page,
connectedPart is null.
You can use IWebPartParameters Interface and it is clearly mentioned on IFilterProvider Interface
[ObsoleteAttribute("Use
System.Web.UI.WebControls.WebParts.IWebPartParameters instead")]
public interface IFilterProvider
Here is a sample which using ...
2
Hmmm...did a little quick digging, found some interesting resources:
A nice write up of the mechanics of how they work. Not completely end user, but not exactly dev-oriented either - MSDN Web Part Connection Overview
A hands on walk through of setting up a connection from the SharePoint Designer Team blog - Creating Master-Detail views with Web Part ...
2
If you think that it is hard from an end user's standpoint, try doing development with it! I think they have simplified it some over the 2003 version.
The one thing that you have to keep in mind is that the data being passed must be defined. There are different "formats" for this contract; Row, Cell, or Parameters. The provider and the consumer must be ...
1
That is a known issue with SharePoint Designer. If you read Maintain, edit, and update PerformancePoint dashboards you'll see the following warning:
Do not click Edit in SharePoint Designer. You cannot use Microsoft SharePoint Designer to edit dashboard pages that contain PerformancePoint Web Parts. Otherwise, data connections to those Web Parts might ...
1
I found why this is happening... the FDLTYPES definition for that buggy field had <Field Name="ParentType">Text</Field>.
When I changed it to Number it started to work. Still, I feel this is a workaround rather than a solution, as the whole thing doesn't behave as expected from the start, but at least the fields work.
1
The error in my case lays in using the CreateChildControls and the OnPreRender functions. I called the provider in the CreateChildControls while it should have been called in the OnPreRender function.
If you call a different Webpart in the CreateChildControls it is possible that the CreateChildControls of that webpart have not been initiated. When ...
1
I think the real reason is that the team that developed these controls initially didn't know how to use web part connections.
But it gives the following advantages (which MS probably will claim is the reason).
Easy setup on single query page
On most search pages users only have a single query. The current implementation makes it easy to add new search web ...
1
What interface are you using? (HINT: post your code ;-)
Standard lists support IWebPartField, IWebPartRow, IWebPartTable and IWebPartParameters. Which you want to use depends on what you want to achieve.
Often you would like to transfer the whole row of data, so you would use IWebPartRow.
...
1
Same happened to me when I tried to send two connections from one provider to one consumer...
I tried this, but I obtained the same error:
A -> B
A -> B
To solve this I created a third WebPart between A and B. In my context it had sense, since the new WebPart had a different use than A. So my result was:
A -> B
A -> C -> B
I hope this can help you.
1
Create two parameters in the class and add another method, like such:
string test1;
string test2;
[ConnectionProvider("People Picker Filter1", "ITransformableFilterValues", AllowsMultipleConnections = true)]
public ITransformableFilterValues SetConnectionInterface()
{
return test1;
}
[ConnectionProvider("People Picker Filter2", ...
1
If this is like what I ran into it 'happens' because of the Page cycle - in other words the WebPart that is supplying the value has to exist before it can supply that value to the WebPart that is consuming it.
As a result you have to handle the data results in the PreRender override.
I may have misunderstood, however, the problem you were having....
1
His webparts need to be within a single updatepanel (With this properties). Consider the following code:
<asp:UpdatePanel ID="updData" runat="server" EnableViewState="true" ChildrenAsTriggers="true" UpdateMode="Always">
<ContentTemplate>
<WebPartPages:SPProxyWebPartManager runat="server" id="spproxywebpartmanager">
...
1
This is how I got it to work.
Create a small serializable class in my provider which implements the interface
the consumer saves its' reference to the class in its' ViewState on PageLoad
the consumer is able to communicate with the provider using the instance of the class staored in the ViewState
WARNING the consumer should first read the value from the ...
1
Have you ruled out all the solutions we suggested on your other post? http://www.sharepointoverflow.com/questions/6753/cant-access-sharepoint-site-from-local-workstation/6754#6754
1
I'm not familiar with this area of Sharepoint, but after looking through those links, it appears that they are actually closely related. Here's my take on it:
The simpler tutorial shows you how to create linked web parts by using a simple interface you define in your own code - IProject - which has nothing but an ID and a name
The advanced tutorial shows ...
1
How did you get the v2 web parts to work in v3? With the .net framework difference I'm not sure how this is possible unless you have the source. I had developed a couple of applications for SPS 2003/WSS 2 that utilized the original web part connection methods that were deprecated. I wasn't able to find a way to easily upgrade or recompile them for ...
1
I think the V2 APIs where in the SharePoint namespace and the connections in the WSS V3 web parts are part of the ASP.NET Namespace. My guess it that is why they are not compatible. I know you can still create a web part using the SharePoint namespace with V3 (not recommended by MS unless you need to). It's possible the web part implementation for consumer ...
Only top voted, non community-wiki answers of a minimum length are eligible
