CSI Score provides a set of prebuilt assets that harmonize data sources, drive scoring logic, and visualize the all-up CSI Score and the composite scores. All assets work together to give admins a jumpstart on company-specific customizations and reduces the time-to-value.
Required Editions
| View supported editions |
| User Permissions Needed | |
|---|---|
| To install CSI Score: |
Customize Application AND Data Cloud Architect permission set AND Tableau Next Admin permission set |
Before you install CSI Score, map the data model objects (DMOs) that the composite scores of CSI Score use as data sources. At least map the Account DMO in Data 360. See Data Requirements for CSI Score.
The installation process uses preset rules to perform a real-time check of your available DMO mappings and automatically tailor CSI Score assets to match your data. While checking the DMOs, the rules consider a DMO as available only if its primary key is mapped. DMOs without a mapped primary key are considered unavailable. The rules then apply these changes to the assets:
- DMOs in CSI Score semantic model:
- Standard DMOs that are unavailable aren’t used or referenced in calculated fields and metrics.
- Transform DMOs aren’t installed if their data sources are unavailable.
- Calculation logic in CSI Score semantic model: Composite score KPIs that source data from unavailable DMOs are excluded from calculations. The rules then adjust the remaining KPI weightage to ensure accurate scoring based only on available data.
- Visualizations and dashboard in Tableau Next:
- Visualizations that show composite scores and KPIs by department, such as Voice of the Customer (VoC) Score by Cloud and NPS by Cloud, exclude representations for departments with missing data sources.
- Visualizations that show KPI relationships for the composite scores exclude representations for the missing KPIs.
- Visualizations that show account watchlists for the composite scores exclude table columns for missing KPIs.
- Batch data transforms in Data 360: Transforms that source data from unavailable DMOs aren’t installed. So, the CSI Score-specific DMOs that store the transformed results are also excluded from the installation.
- From Setup, in the Quick Find box, enter CSI Score (Beta), and then select CSI Score (Beta).
-
Expand Set Up the CSI Score Application (Beta) and click
Install.
It takes around 30–60 minutes for all the CSI Score assets to install. Refresh the page to track the installation. To get more granular information about the installation process, go to App Hub in Setup.
These assets are added on installation:
| Asset Type | Assets |
|---|---|
| Data 360 |
|
| Tableau Next |
A new workspace that contains:
The new workspace is also associated with the installed CSI Score semantic model and its DMOs. |
| App | The CSI Score Lightning app where the Tableau Next assets are available for business executives. |
Why Is a Logical View in the Installed CSI Score Semantic Model Unavailable?
Logical views in semantic models aggregate data from multiple DMOs. A logical view is available for use only when all fields from its source DMOs are mapped.
To resolve this, identify the specific DMOs that power the unavailable logical view and map all fields within those DMOs.
What Happens If I Map More DMOs After Installation?
Installation rules automatically configure the semantic model to exclude unmapped data sources. To include newly mapped DMOs in calculated fields, you must reinstall CSI Score.
Why Do Some Visualizations Show an Error Even Though Source DMOs Are Mapped?
During installation, DMOs are considered available if their primary keys are mapped. However, CSI Score resources such as KPIs and composite scores can require data from other DMO fields. If these specific fields are unmapped, the visualizations that rely on them show an error.
For example, NPS by Cloud sources data from several DMOs. While installation rules automatically adjust calculation logic to exclude unavailable DMOs, the calculation logic isn’t automatically adjusted for DMOs that are available but missing the required field mappings. In this scenario, the visualization for NPS by Cloud shows an error.
