Cross-page Web Part Connections
Some interfaces can be used to connect a Web Part on one page (the source page) to a Web Part on a different page (the target page). The behavior is similar to a hyperlink.
You should keep the following about cross-page connections in mind:
- A Web page editor that is compatible with Microsoft® Windows® SharePoint™ Services, such as Microsoft Office FrontPage® 2003 is required to author cross-page connections. However, once a cross-page connection has been formed, it can be used by any supported Web browser at run time.
- Only connectable Web Parts that have implementations designed to run on the server (CanRunAt = ConnectionRunAt.Server or CanRunAt = ConnectionRunAt.ServerAndClient ) can establish cross-page connections. Connections that are formed on the client side are not allowed to cross Web Pages.
The following table shows the interfaces that can be connected across pages.
| Source page interface | Target page interface |
|---|---|
| IRowProvider | IFilterConsumer |
| IRowProvider | IParametersInConsumer |
| IFilterProvider | IFilterConsumer |
| IParametersOutProvider | IParametersInConsumer |
| IParametersInProvider | IParametersInConsumer |
When working with cross-page Web Part connections, you must:
- Pass ConnectionRunAt.Server or ConnectionRunAt.ServerAndClient to the runAtOptions parameter of the RegisterInterface(String, String, Int32, Microsoft.SharePoint.WebPartPages.Communication.ConnectionRunAt, object, String, String, String, Boolean) method
- Pass true to the allowCrossPageConnection parameter of the RegisterInterface(String, String, Int32, Microsoft.SharePoint.WebPartPages.Communication.ConnectionRunAt, object, String, String, String, Boolean) Method
- Implement the GetInitEventArgs method to provide specific information about data that is passed through the connection interface.
For information about creating connectable Web Parts, see Creating a Connectable Web Part.