> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release7.2/dashboards/data-quality-last-execution-dashboard.md).

# Data Quality Last Execution Dashboard

The Data Quality Last Execution Dashboard provides insights into the total number of objects associated with different dimensions. It categorizes objects based on their data quality status, allowing data analysts to track data integrity and performance across multiple dimensions.

This report is essential for evaluating data quality across dimensions. By showcasing object validation results, it helps data teams identify issues and take corrective actions to improve data integrity. Additionally, it retrieves the most recent execution ID for each object and rule to ensure that only the latest validation results are considered.

### Execute the Advanced Job for the Dashboard

1. Navigate to Administration > Advanced Jobs.
2. In the Name column, search for&#x20;

   1. Build DashboardStats &#x20;
   2. Enable system dashboards

   <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeni_bPsrgD-TY1nUtS9tI0Wueq1FPOad2pw2F7_cQK5-E4a6GCF71n2s7I_Axv04ljSwhJqyZt-l-JJiAkBNtiXMrw0IVBECl28R-_jn7fQp1xj6xKRwjfe4x9qyuhmJKcjrld4A?key=X6kUPx3teEjaqtT5hVkT1IF3" alt=""><figcaption></figcaption></figure>
3. Select the Advanced Job.
4. Click Run Advanced Job to trigger the job.
5. Monitor the Job Home Page for the execution status.
6. Once the job executes successfully, the reports will be generated and displayed under Data Catalog Reports.

   <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeBNUeb16imARfcqG9LsAH39paqk5Nau1u_Cvp_IRqEjpjOa9JrNu6SqTn4xUghzjQGkkAuCG79Y9L87DS0ItK3ThaCbcLu4ccTpwoYnQ7vwS5R4vnOhtc-O2QF1Ifhf1dVIVfG?key=VTFj6o4PEh4-7qMuY5FTFA" alt=""><figcaption></figcaption></figure>

### **Purpose**

* Display the total count of attributes associated with each dimension.
* Categorize attributes based on data quality status into:
  * Passed
  * Failed
  * Execution Failed
  * Undetermined
  * Total
* Retrieve the most recent execution ID for each object and rule.
* Ensure that only the latest validation result is used.

### Key Performance Indicators (KPI)

| KPI Metric                             | Description                                                                          |
| -------------------------------------- | ------------------------------------------------------------------------------------ |
| Successful Object Validations (Passed) | Counts the number of objects (columns) that successfully met data quality standards. |
| Failed Object Validations              | Represents the number of objects that did not pass data quality checks.              |
| Total Object Validations               | Measures the total number of objects assessed for data quality.                      |
| Execution Failures                     | Tracks validation failures caused by execution errors.                               |
| Undetermined Objects                   | Identifies objects with inconclusive validation results.                             |


---

# 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.ovaledge.com/release7.2/dashboards/data-quality-last-execution-dashboard.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.
