> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba-schema-workbench/pdia-9.3-schema-workbench/adapt-mondrian-schemas-to-work-with-analyzer/step-5-disable-drill-through-links.md).

# Step 5: Disable drill-through links

You can permanently disable drill-through links for all analysis reports by editing the `analyzer.properties` file, or you can disable drill-through links on a cube-by-cube basis. Both methods are described in the steps below.

1. Global Disable: Perform these steps to disable drill-through links for all cubes and analysis data sources.

   1. Open your `analyzer.properties` file with a text editor and find the property called **report.drill.links.disabled**.
   2. Set the value from *false* to *true* as shown here.

      From:

      ```
      report.drill.links.disabled=false
      ```

      To:

      ```
      report.drill.links.disabled=true
      ```

   Drill-through links are now disabled for all cubes and analysis data sources. The option for drill-through links is no longer visible on the Report Options dialog box.
2. Individual Cubes: Perform these steps to disable drill-through links on a cube-by-cube basis.

   1. Open the schema for the particular cube on which you want to disable drill-through links.
   2. Find the Cube element in the schema file and add this annotation to disable the links:

      ```
      <Annotations><Annotation name="AnalyzerDisableDrillLinks">true</Annotation></Annotations>
      ```
   3. Save and close the schema.

   Drill-through links are now completely disabled for that cube, and the option to show drill-through links is no longer visible on the Report Options dialog box for the cube.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pba-schema-workbench/pdia-9.3-schema-workbench/adapt-mondrian-schemas-to-work-with-analyzer/step-5-disable-drill-through-links.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.