Skip to main content

Connect SharePoint Web Parts Programmatically

The task

Send data from one Web part to another. Scenario could be like one Web part contain the list of items - say video, images or clothes catalog - and the other Web part displays detailed view of the catalog item.

Solution

1. Create Web part which will send data - data producer.

1.1. When the Web part class is created we need to inherit that class from ICellProvider. The class definition will look like the following:

public class DataProviderWebPart : Microsoft.SharePoint.WebPartPages.WebPart, ICellProvider
{
...
}

1.2. Define the following properties:

public event CellProviderInitEventHandler CellProviderInit;
public event CellReadyEventHandler CellReady;
private int _nCellConnectedCount = 0;
private string _sCellInput;
private string _sCellName;
private string _sCellDisplayName;

1.3. Override the following methods: EnsureInterfaces, CanRunAt, PartCommunicationConnect, PartCommunicationInit, PartCommunicationMain, CreateChildControls.

public override void EnsureInterfaces()
{
//Registers an interface for the Web Part
RegisterInterface("MyCellProviderInterface_WPQ_", InterfaceTypes.ICellProvider, Microsoft.SharePoint.WebPartPages.WebPart.UnlimitedConnections, ConnectionRunAt.Server, this, "CellProviderInterface_WPQ_", "Provide data to others", "Provides some data to everyone");
}

public override ConnectionRunAt CanRunAt()
{
//This Web Part can run on the server
return ConnectionRunAt.Server;
}

public override void PartCommunicationConnect(string interfaceName,
Microsoft.SharePoint.WebPartPages.WebPart connectedPart,
string connectedInterfaceName,
ConnectionRunAt runAt)
{
EnsureChildControls();

if (interfaceName == "MyCellProviderInterface_WPQ_")
{
_nCellConnectedCount++;
}
}

public override void PartCommunicationInit()
{
if (_nCellConnectedCount > 0)
{
if (CellProviderInit != null)
{
CellProviderInitEventArgs cellProviderInitArgs = new CellProviderInitEventArgs();
cellProviderInitArgs.FieldName = _sCellName;
cellProviderInitArgs.FieldDisplayName = _sCellDisplayName;
CellProviderInit(this, cellProviderInitArgs);
}
}
}

public override void PartCommunicationMain()
{
if (_nCellConnectedCount > 0)
{
if (CellReady != null)
{
CellReadyEventArgs cellReadyArgs = new CellReadyEventArgs();
cellReadyArgs.Cell = ... // here you initialize your Cell value which is the data you want to send to other Web part

CellReady(this, cellReadyArgs);
}
}
}

protected override void CreateChildControls()
{
_sCellName = "CellInput";
_sCellDisplayName = "CellDisplayInput";
}

2. Create Web part which will consume data - data consumer. Implement properties and methods that will allow us to receive data from other Web parts.

2.1. When the Web part class is created we need to inherit that class from ICellConsumer. The class definition will look like the following:

public class DataProviderWebPart : Microsoft.SharePoint.WebPartPages.WebPart, ICellConsumer
{
...
}

2.2. Define the following properties:

public event CellConsumerInitEventHandler CellConsumerInit;
private string _sInterfaceRegistrationError = string.Empty;
private bool _bWebpartConnected = false;
private int _nCellConnectedCount = 0;
private string _sCellName = "MediaPlayerCellData";
private string _sConnectedFieldName = string.Empty;
private string _sConnectedWebpartName = string.Empty;
private Label _lblDisplayLabel;

2.3. Override the following methods: EnsureInterfaces, CanRunAt, PartCommunicationConnect, PartCommunicationInit, GetInitEventArgs.

public override void EnsureInterfaces()
{
try
{
RegisterInterface("MyDataConsumer_WPQ_", "ICellConsumer", Microsoft.SharePoint.WebPartPages.WebPart.UnlimitedConnections, ConnectionRunAt.Server, this, "CellConsumerClientInterface_WPQ_", "Data consumer", "Consumes the data from another Web part");
}
catch (SecurityException ex)
{
_sInterfaceRegistrationError = ex.ToString();
}
}

public override ConnectionRunAt CanRunAt()
{
//This Web Part can run on the server
return ConnectionRunAt.Server;
}

public override void PartCommunicationConnect(string interfaceName,
Microsoft.SharePoint.WebPartPages.WebPart connectedPart,
string connectedInterfaceName,
ConnectionRunAt runAt)
{
EnsureChildControls();

if (interfaceName == "MyDataConsumer_WPQ_")
{
_bWebpartConnected = true;
_nCellConnectedCount++;
}
}

public override void PartCommunicationInit()
{
if (_nCellConnectedCount > 0)
{
if (CellConsumerInit != null)
{
CellConsumerInitEventArgs cellConsumerInitArgs = new CellConsumerInitEventArgs();
cellConsumerInitArgs.FieldName = _sCellName;
CellConsumerInit(this, cellConsumerInitArgs);
}
}
}

public override InitEventArgs GetInitEventArgs(string InterfaceName)
{
if (InterfaceName == "MyDataConsumer_WPQ_")
{
EnsureChildControls();

CellConsumerInitEventArgs cellConsumerInitArgs = new CellConsumerInitEventArgs();
cellConsumerInitArgs.FieldName = _sCellName;
return (cellConsumerInitArgs);
}
else
return (null);
}

2.4. Implement the following ICellConsumer methods: CellProviderInit, CellReady.

public void CellProviderInit(object sender, CellProviderInitEventArgs cellProviderInitArgs)
{
this._sConnectedFieldName = SPEncode.HtmlEncode(cellProviderInitArgs.FieldDisplayName);
}

public void CellReady(object sender, CellReadyEventArgs cellReadyArgs)
{
if (cellReadyArgs.Cell != null)
{
... // here you define what you would like to do with the data consumed
}
}

3. Enjoy the solution :)

Real life sample

I used the approach above to implement video library and video player Web part on the SharePoint Web site.

There is a list of video URLs - video catalog.



On the SharePoint page I added two Web parts: one which displays videos from the Movies list and another one which plays the video from that URL in the embedded video player.






Initially the video player Web part is blank, because it's not connected to the Web part which will provide us with video URL. We needed to connect them. In the Modify Shared Web Part - Connections menu appropriate Web part was selected.



Now when we select videos from the list they are displayed in the player.







Comments

Popular posts from this blog

Setting up External Content Type for SQL Server database using SQL Server authentication - SharePoint 2010 Foundation

This post is a follow up on the issues that I have got setting up External Content Type (ECT) on SharePoint 2010 Foundation that was going to connect to remote SQL Server database for information. I cannot use my SharePoint user accounts to access SQL Server. According to the information I have discovered ECT and Business Connectivity Services are available in the SharePoint 2010 Foundation, but there are some issues if you want to use authentication methods in your external connections that are different from Windows Identity or Current User Identity. This is because there is no Secure Store Service in SharePoint 2010 Foundation which serves as an impersonation hub and is only available in SharePoint 2010 Server edition. The issues are coming from the fact that you can actually create ECT in SharePoint Designer 2010 providing just Secure Store ID and system would ask you for credentials and here you go, but when you try to use your ECT in External Lists or as a lookup columns you w...

SharePoint 2013 Development and Consulting - Laptop & Conferencing Experience with Lync

Have just jumped on a brand new SharePoint 2013 massive Intranet project and because of specific working conditions have found some items that required addressing almost immediately in order to continue the job. Maybe this will be interesting to someone else who is about to start SharePoint 2013 development to have an idea of what might be necessary. I started working with SharePoint using my own infrastructure in 2009. I used iMac with 320GB HDD and 4GB RAM running VMWare Fusion to virtualise Windows  environment ( SQL Server 2008, standalone SharePoint 2007, Visual Studio 2008, Office 2007). It was all-in-one virtual machine. A bit slow, but enough for any SharePoint work that I had at that time. For communication with colleagues and partners we used GoToMeeting . Great tool that worked (and still works) without any problems. Voice, video, screen-sharing - all worked well using built-in audio/video hardware. In 2010 I got a MacBook Pro  with 500GB HDD and 8GB ...

InfoPath 2013 Preview - URL not valid error when publishing

In InfoPath 2010 there is a problem when you try to publish a Form to a SharePoint site that doesn't have root site collection. You will get an error message "The following url is not valid". It's described here:   http://support.microsoft.com/kb/981854 The solution is to create root site collection for the Web application. Same problem is with InfoPath 2013: In my situation I didn't create the root site collection initially, but used "/sites" managed path instead for all site collections. To solve the problem with InfoPath I had to create it. Used a new site template "Project Site". Will get a chance to research that too. :)