# v4.35

## Release highlights <a href="#v4.23-releasehighlights" id="v4.23-releasehighlights"></a>

### 1. Quality implementations self-join <a href="#v4.23-1.structuresnotesworkflowandversions" id="v4.23-1.structuresnotesworkflowandversions"></a>

When creating a new implementation, you can now join a table to itself. The same table is specified twice but with two different aliases. These table aliases can be edited.

![](/files/8ov42ozuiEouYjj71fyf)

## Features and fixes delivered with this release <a href="#v4.23-featuresandfixesdeliveredwiththisrelease" id="v4.23-featuresandfixesdeliveredwiththisrelease"></a>

### Features <a href="#v4.23-features" id="v4.23-features"></a>

* TD-4390 As a quality user I want to create an implementation joining a table with itself
* TD-4379 Avoid indexing grants for class = field structures
* TD-3393 Include implementation dynamic information in td-metrics

### Fixes

* TD-4388 Lineage is not being displayed in corresponding tab from data catalogs
* TD-4413 Lineage and impact tabs in data catalog are not working correctly
* TD-4387 Some lineage requests are blocking the browser
* TD-4380 Filters applied to an operator in quality implementations does not allow to cast value
* TD-4180 Application does not allow to change implementation key for raw implementations
* TD-4356 Remove number of metadata fields in structure types view in order to improve performance
* TD-4369 504 error on /api/data\_structure\_types call


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.truedat.io/v6.7/release-notes/v4/v4.35.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
