> 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-dashboard-designer-cp/advanced-topics/use-content-linking-to-create-interactive-dashboards/link-an-analyzer-report/create-graphic-element-links-to-a-report.md).

# Create graphic element links to a report

You can create content-to-content links between an Analyzer chart and any other parameterized report such as a Report Designer report, a data table, or another Analyzer report.

Below are general instructions for linking an Analyzer chart to a report. You must adjust the instructions when working with your own data.

1. Create a simple dashboard that contains an Analyzer chart and a parameterized report.

   The example here displays an Analyzer chart and an Analyzer report displayed as a table view. At this point, none of the content has been linked and you have a "static" dashboard.

   Hypothetically, if you want users to be able to click a bar in the bar chart and update the Analyzer table view, the table must contain at least one parameter. In the example below, there are two parameters, (LINE and TERRITORY), associated with the Analyzer table.

   ![Parameter created for LINE](https://1610525749-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdbSFXbJFiObHB299lSSa%2Fuploads%2Fgit-blob-215662b9606892c263767202dafd4e06dfed79bf%2FAnalyzer_param_on_line_ONYX.png?alt=media)
2. Under **General Settings**, choose the Analyzer chart, then click the **Content Linking** tab.
3. Click the check box (or check boxes) next to the field/column name you want enabled for content linking, and then click **Apply**.

   ![Chart content linking](https://1610525749-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdbSFXbJFiObHB299lSSa%2Fuploads%2Fgit-blob-8ce47ffc9e982fd133a4a1eb96c56518bef7bcc7%2FAnalyzer_chart_content_linking_sample_ONYX.png?alt=media)
4. Under **General Settings**, choose the Analyzer report (table view) and click the **Parameters** tab.
5. Click the down arrow in the **Source** text box to display another source for the parameters you created.

   In the example below, notice that **Sales by Line**, (this is the name of the dashboard panel that contains the chart), can now be selected as a source for both the **TERRITORY** and **LINE** parameters.

   ![Select source on Parameters tab](https://1610525749-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdbSFXbJFiObHB299lSSa%2Fuploads%2Fgit-blob-b2e6167c1291da2aa6a949594f3b9ab6b77408b3%2FAnalyzer_content_linking_selections_territory_ONYX.png?alt=media)
6. Save your dashboard.

   See [Saving Dashboards](/pba/pentaho-dashboard-designer-cp/save-a-dashboard.md) for steps.

In this example, content linking is applied when users double-click a bar in the bar chart. The data table updates and displays sales details for a product line in a specific territory.

![Content linking example](https://1610525749-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdbSFXbJFiObHB299lSSa%2Fuploads%2Fgit-blob-e02769be3e7dba08bd38a869a4ae152eac7bb6e9%2FAnalyzer_chart_content_linking_final_ONYX.png?alt=media)


---

# 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-dashboard-designer-cp/advanced-topics/use-content-linking-to-create-interactive-dashboards/link-an-analyzer-report/create-graphic-element-links-to-a-report.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.