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
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.
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.
...
Only top voted, non community-wiki answers of a minimum length are eligible
