> 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/pentaho-analyzer-cp/advanced-topics/defining-hyperlinks-cp/create-default-hyperlinks.md).

# Create default hyperlinks

You can specify a default hyperlink for a dimension in a report, instead of going to each report containing that dimension and enabling the hyperlink functionality. Default hyperlinks are configured in the schema.

Perform the following steps to create default hyperlinks:

1. Open the Mondrian schema file in which you want to activate the hyperlink feature.

   **Note:** The Schema Workbench tool is recommended for editing schemas.

   ![Schema workbench](https://1610525749-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdbSFXbJFiObHB299lSSa%2Fuploads%2Fgit-blob-7b9fdfb5c5c8a566d3a39ed49cb2d8b02c06b14d%2FPAZ%20Schema%20workbench.png?alt=media)
2. In your chosen dimension, add a new annotation named `AnalyzerHyperlink`.
3. Insert the desired hyperlink for the selected dimension as the CDATA attribute.
4. Save your changes to the schema file.

**Note:** In this example an annotation was created on the `Customer` dimension, and the hyperlink associated with that dimension is `http://search.yahoo.com/search?p={Customer}` Dimension values are case sensitive, so the dynamic value needs to exactly match the dimension. In this example `customer` will not work.


---

# 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/pentaho-analyzer-cp/advanced-topics/defining-hyperlinks-cp/create-default-hyperlinks.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.