This sample shows you how to create a link that passes filter values from SAS BI Dashboard to an OLAP-based SAS Web Report Studio report.
In order for the SAS® OLAP Server to resolve the report filter, the full OLAP path (unique name) of the filter value must be passed to SAS Web Report Studio. In an OLAP cube, the full path to a level is [Dimension].[Hierarchy].[All Member].[Level]
. The following display is created from the sample Orion Star cube. In this example, the Customer Group
display value is Orion Club Gold members
. The Customer Group
full OLAP path (unique name) is [Customers].[Customers].[All Customers].[Orion Club Gold members].
Note: Although you can create a new OLAP category data item in SAS® Information Map Studio, this type of data item is treated as a measure. If you reference an OLAP category data item in an indicator data, you see an "unparseable number" error.
This sample is for advanced users. It assumes that you are proficient using SAS BI Dashboard, SAS Web Report Studio, and SAS Information Map Studio.
This sample was written using the following software versions:
This example uses a SAS OLAP cube created from the Orion Star sample data.
This sample shows you how to perform these steps:
The following sections review these steps.
Using SAS Information Map Studio, create an information map that is based on the Orion Star cube. Include a prompted filter for Customer Group, and be sure to provide a default value. The following displays illustrate the process.
Use SAS Web Report Studio to create a filtered report based on the information map that you created previously. The following displays illustrate the process.
Create a data table from an OLAP cube that includes the full OLAP path for the value that is used to link the dashboard to the report. Here is sample code that you can use to create a data table from Orion Star.
Be sure to include PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME
in the SQL query. Including PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME
is required for the following tasks:
MEMBER_CAPTION
).MEMBER_UNIQUE_NAME
).These fields in the wrs.OrionStar_CustomerGroup
table are needed for this example:
Field | Label | Sample value | Purpose on dashboard |
---|---|---|---|
Customer_Group |
[Customers].[Customer_Group].[MEMBER_CAPTION] |
Orion Club Gold members |
This field is used to display values in a spark table |
Customer_Group 1 |
[Customers].[Customer_Group].[MEMBER_UNIQUE_NAME] |
[Customers].[All Customers].[Orion Club Gold members] |
This field contains the value that is passed in a link to the filtered report. (The report is defined on a spark table.) |
The following display shows the table created from the Orion Star cube:
Here are the created dashboard objects.
Name | Dashboard component type |
---|---|
0_DAT_CustomerGroup | Indicator Data |
0_DAT_Year* | Indicator Data |
0_IND_OrionStar_Table | Spark Table Indicator |
0_IND_Year_Prompt* | Dynamic Prompt Indicator |
0_OrionStar_LinkToWRS | Dashboard |
*These dashboard objects are not a required part of the design to link a dashboard to a report. |
Note: The BID_WRS
library reference must be pre-assigned for the pooled workspace server to use this library with the SQL source type.
Here are the specific steps for this task.
Note: Be sure to use the displayed text for the prompt when defining the link to the report.
The following display shows that you can now click on a customer group in the spark table in order to display a report that is filtered by the selected customer group.
For more information about creating cubes, see the SAS OLAP Server and SAS OLAP Cube Studio documentation pages.
For a list of available documentation for SAS BI Dashboard, see the SAS BI Dashboard documentation page.
For more information about SAS Web Report Studio, see the SAS Web Report Studio documentation page.
For more information about SAS Information Map Studio, see the SAS Information Map Studio documentation page.
These sample files and code examples are provided by SAS Institute Inc. "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Recipients acknowledge and agree that SAS Institute shall not be liable for any damages whatsoever arising out of their use of this material. In addition, SAS Institute will provide no support for the materials contained herein.
These sample files and code examples are provided by SAS Institute Inc. "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Recipients acknowledge and agree that SAS Institute shall not be liable for any damages whatsoever arising out of their use of this material. In addition, SAS Institute will provide no support for the materials contained herein.
Type: | Sample |
Date Modified: | 2013-12-11 09:24:14 |
Date Created: | 2013-10-18 15:30:20 |
Product Family | Product | Host | Product Release | SAS Release | ||
Starting | Ending | Starting | Ending | |||
SAS System | SAS BI Dashboard | z/OS | 4.31_M2 | 9.3 TS1M2 | ||
Microsoft® Windows® for x64 | 4.31_M2 | 9.3 TS1M2 | ||||
64-bit Enabled AIX | 4.31_M2 | 9.3 TS1M2 | ||||
64-bit Enabled Solaris | 4.31_M2 | 9.3 TS1M2 | ||||
HP-UX IPF | 4.31_M2 | 9.3 TS1M2 | ||||
Linux for x64 | 4.31_M2 | 9.3 TS1M2 | ||||
Solaris for x64 | 4.31_M2 | 9.3 TS1M2 |