# v4.18

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

### 1. Selection of fields to apply profiling to <a href="#v4.18-1.selectionoffieldstoapplyprofilingto" id="v4.18-1.selectionoffieldstoapplyprofilingto"></a>

With this new version users will be able to request profiling to be executed selecting multiple fields for a given table. This option will only be available for those tables from sources that have profiling option activated. In order to have this feature producing profiling results new versions of the connectors will need to be depoyed.

![](/files/-MaJIV6QzJUXdyQs6ZhN)

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

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

* TD-3108 - As Data Catalog user I want to select to which fields in my structure I want to apply profiling to

### Fixes  <a href="#v4.18-fixes" id="v4.18-fixes"></a>

* TD-3471 - Create tests for all operators in SQL Server and fix currently failing operators
* TD-3472-When we try to delete an implementation linked to an execution group we get an error
* TD-3494 - Implementation and Rule are not being reindexed when a rule result is loaded individually
* TD-3505 - Data source of native implementations is not being indexed, so connector doesn't find them when filtering by source
* TD-3566 - Avoid having structures without parent displayed on the main system page
* TD-3509 - Data is not being displayed correctly for quality rules with number of errors type of analysis defined


---

# 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/v8.4/release-notes/v4/v4.18.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.
