Debug an Analysis

Learn how to troubleshoot why an analysis is missing content.

Overview

Within an analysis, administrators can view a report that provides details on what content is being dropped or hidden from the user.

If a user’s data security access is insufficient or if the data is not configured, Visier will drop or hide visualizations or content that are impacted.

Guidebook topics and entire Guidebooks can be dropped if:

  • A Guidebook is not assigned to a user through a content package.
  • A Guidebook topic does not contain at least one valid topic. A topic is considered valid if it has at least one valid analysis and is assigned access through a content package.
  • An analysis does not pass a check by Visier to ensure all objects used in a visualization (metrics, dimensions, and concepts) are available and deployed correctly. Analyses pass the check if they have at least one visualization or linked analysis that the user is permitted to view. If an analysis does not pass the check, that topic will be unavailable to the user.

When rendering an analysis, certain content may be dropped if:

  • Any objects used in a visualization are invalid. For example, due to lack of permitted access by a specified user.
  • A linked analysis does not contain any valid visual contents (visualizations, carousels, images, or linked analyses).
  • A carousel does not include at least one valid visualization.
  • A business question does not contain any valid visualizations.

You can use the analysis debug report to identify the specific cause of dropped or hidden visualizations, including:

To debug an analysis for a user, the administrator must preview the solution as that user.

You may want to debug an analysis to:

  • Test that the analysis is working as expected for your target user.
  • Troubleshoot why your users aren’t seeing all the information in an analysis.

Step One: Preview a user

To investigate the content that is missing for a user, you must preview the solution as that user.

  1. Open the studio experience.
  2. On the global navigation bar, click Tenant > Users.
  3. Select the user that is missing content in an analysis.
  4. In the upper-right corner, click Preview As User.

Step Two: Retrieve the analysis debug report

To retrieve the debug report, you must access the analysis while previewing the affected user.

  1. In the solution experience, navigate to an analysis that is missing content for the user.
    • On the navigation bar, click Analyses and select an analysis from the list.
    • On the navigation bar, click Guidebooks and select a topic from the list.
  2. In the upper-right corner, click the Show analysis debug report button .

    This shows the debug information for the analysis, including the chart title and a message about the hidden content. If the chart title is not available, the chart ID is shown.

  3. Optional: To download a spreadsheet with more information about the user’s access, click User data access report.

    This report contains additional context for hidden content. For more information, see User data access report.

Step Three: Resolve the hidden content issues

Now that you know what content is hidden in an analysis, you can take steps to resolve the issues to allow the user to see that content, if required.

  • If content is hidden due to data security, you can assign the appropriate access using permissions. For more information, see Permission Management.
  • If content is hidden due to unconfigured metrics or concepts, you can configure the relevant objects in the studio experience. For more information, see Work with Metrics and Concepts.
  • If the content is hidden due to a lack of loaded data, you can upload data to Visier. For more information, see File Upload.
  • If the content is hidden due to unpopulated dimensions or properties, check its mappings or associated business rules.

User data access report

The user data access report is an XLSX file. The spreadsheet has two sheets:

  • Design Objects Data Properties Info: The user’s access to all data properties associated with invisible content objects.
    • The Access Level column defines the user’s access to the data property as Aggregate, Detailed, None, or Unassigned.
    • The Data Loaded column defines whether or not data is loaded for the data property.
  • Unconfigured Concepts Info: The concepts in the analysis that aren’t configured. This sheet is only available if there are unconfigured concepts used in the analysis visualizations.

Example: Previewing Jane Smith to investigate hidden visualizations in the Hire Talent analysis

Let’s say that you’re an administrator and one of your users, Jane Smith, told you that they think the Hire Talent analysis isn’t showing all the information that the user expects it to.

To investigate, you preview the solution as Jane Smith and navigate to the Hire Talent analysis, open the analysis debug report, and then download the user data access report.

The Design Objects Data Properties Info sheet provides the following information:

  • The Offer Accepted Ratio metric has a property called Close Reason that the user has no data access to. This means the user’s data permissions prohibit them from seeing data for Close Reason.
  • The New Hire Quality Survey Score metric has a property called Overall Quality of Hire that the user is not assigned access to. This means the user’s data permissions do not address the user’s access to Overall Quality of Hire.
  • The Time in Stage (Applicant Process) metric is missing a property.

The Unconfigured Concepts Info sheet provides the following information:

  • The Offer Accepted Ratio metric has an unconfigured concept called Offer Accepted.

From the above information, you can take action to resolve the hidden content for Jane, including:

  • If appropriate, give Jane data access to the Close Reason and Overall Quality of Hire properties.
  • Look for and configure the property that is missing from Time In Stage (Applicant Process).
  • Configure the Offer Accepted concept.