Connections are used to pass values between Web Parts in a SharePoint BI or PerformancePoint dashboard. They allow content displayed within different Web Parts on a page to be coordinated and synchronized. This is central functionality in PerformancePoint as you might imagine.
A connection is made between a provider Web Part and a consumer Web Part.
The Web Part that sends a value is called a provider. Provider Web Parts will have one or more begin-points. A begin-point is a source of values of a given type that can be supplied by the provider.
The Web Part that receives a value is called a consumer. Consumer Web Parts will have one or more end-points. An end-point is a destination for values of a given type that can be used in some way by the consumer Web Part.
A connection is made between a provider begin-point and a consumer end-point. A given Web Part can be either a consumer or provider, or both. Circular connections are prohibited.
The following is a list of begin-points available in PPS filters or scorecards.
Member Unique Name
A fully qualified member name. In many cases this is an Analysis Services Member name. This can also be a member set expression or calculated member expression.
Member Display Name (caption)
The display value associated with the member. This is the value you see when the member is displayed in a report or scorecard.
PerformancePoint time intelligence formula
As the name suggests, a date time value
The value of a custom property (scorecard only)
An XML blob containing all the data and contextual information associated with a scorecard cell. (scorecard only)
The following shows which begin-point can be used when connecting to PPS reports.
The following table is a list of end-points available in PPS reports.
Page / Background
Potentially any value. Usually a member unique name, display name or text value
A date time value. Scorecard only.
This is used in PPS to set the current date for time intelligence.
Cell Context (scorecard only)
The Tabular Filter can be thought of as the catch all. It emits a particular cell value from a tabular data source. This value can be a member, caption, number, or text value. It is a good filter to keep in mind when you need to work with multiple data sources or complex set expressions in MDX
Any (depends upon the content of the column cell)
The MDX filter allows you enter an MDX set expression. Since this filter requires an MDX statement it works with Analysis Services data sources only.
Members: Column Member, Row Member, Page, Hierarchy, Parameter
Display Name (caption)
Text and Members when connection formula is used
The member selection filter allows can send member values from an Analysis Services or tabular data source to a report or scorecard.
* Analysis Services data sources only.
The standard time intelligence (TI) filter allows users to enter one or more TI Formula expressions. The formula can can be evaluated by the filter for any of the data sources mapped in the filter. The filter can also send the formula as is. This is useful for reports like the scorecard that can evaluate TI formula internally.
Time Intelligence Formula
Data Source (Multiple by name)
The time intelligence calendar filter allows users to choose a date. The supplied date will be used when evaluating the TI formula. Unlike other filters, Connection formula is required for this filter. The user must enter a TI formula expression when the connection is created or the filter will not work properly. As with the standard TI filter, one or more data sources can be used. The Member Unique Name and Display Name begin-points will be replicated for each mapped data source.
Uses default data source
DateTime (scorecards only)
* Time Intelligence must be entered in the filter connection formula dialog for this filter to work.
The scorecard is the only report type Web Part available in PerformancePoint that can both send and receive filter values. The filter values are emitted either when the scorecard is rendered or when a scorecard cell is clicked.
Context (KPI Details report only)
About the Author: Stephen Handy is a Program Manager on the PerformancePoint Services SharePoint BI team.