> For the complete documentation index, see [llms.txt](https://academy.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pentaho.com/pentaho-ctools/c-tools/community-data-access.md).

# Community Data Access

Access data sources ..

{% hint style="info" %}

#### Understanding CDA for Dashboard Data Integration

Community Data Access (CDA) is a powerful Pentaho plugin that simplifies dashboard data management. While Pentaho offers multiple data access methods - including XMLA and Kettle transformations as web services - CDA stands out for its ease of use and flexibility.
{% endhint %}

{% hint style="info" %}

#### Key Features and Capabilities

&#x20; • Direct access to various data sources

&#x20; • Parameter-driven queries for targeted results

&#x20; • Built-in data preview functionality

&#x20; • Data manipulation and transformation tools

&#x20; • Export options to standard formats

&#x20; • Ability to combine multiple data sources through joins and unions
{% endhint %}

{% hint style="info" %}

#### Implementation Approaches

CDA accommodates both code-free and programmatic implementations. While you can create data sources without writing code, understanding the underlying XML structure and coding principles provides deeper insights into CDA's functionality.

The beauty of CDA lies in its simplicity - whether you prefer visual tools or hands-on coding, you can effectively:

&#x20; • Configure data sources

&#x20; • Design custom queries

&#x20; • Transform data outputs

&#x20; • Create dashboard-ready datasets

This streamlined approach eliminates the need for complex data parsing, making dashboard development more efficient and accessible.
{% endhint %}


---

# 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://academy.pentaho.com/pentaho-ctools/c-tools/community-data-access.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.
