> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/delpha-for-salesforce/delpha-upgrade/upgrade-tasks/build-3.95.x/build-3.95.0-04trl0000024ia5iam.md).

# Build 3.95.0 (04tRl0000024IA5IAM)

{% hint style="info" %}
Add this path to your org URL:\
`/packaging/installPackage.apexp?p0=04tRl0000024IA5IAM`
{% endhint %}

## What's New&#x20;

### Duplicate

**Data Steward**:&#x20;

* **Steward Yes / Processed = False**: Are now kept when doing Evaluate
* **Record Name**: Now follow the standard colour code (red = different).&#x20;

### LinkedIn

* **Contact LinkedIn Profile search**: Use Account LinkedIn company name when available for better contact LinkedIn profile sourcing
* **Account LinkedIn enrichment**: If there is a current LinkedIn profile, all corresponding data will be available upon initial assessment result. Data for the current LinkedIn will be displayed in the Delpha fields and on the Score Meter.

### Campaign

* **Sales Navigator Import**: Improved messages on the Import step.&#x20;

### Steward View

* **Steward View headers**: Add a wrap column head toggle on both steward views (data and duplicate)
* **Assess Current Field only**: On the Data Steward View, you can now choose to assess your selected records on all teh monitored field or only on the one you are working one. Faster assessments, more control on the scope.

## Fixes

### Duplicate

* **Merging rules**:&#x20;
  * **Visibility in Merge Editor**: Fix merge field rule visibility toggle, not saved for selection field.
  * **Merging rules troubleshooting**: Flag merge field rules whose selection field does not exist
* **Merge Editor**: Hide a group's selection field when it is not the display field


---

# 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://help.delpha.io/delpha-for-salesforce/delpha-upgrade/upgrade-tasks/build-3.95.x/build-3.95.0-04trl0000024ia5iam.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.
