# External Unique ID Validation

## External Unique ID Validation

#### Introduction

Now users no longer have to worry about the possibility of '**External Unique ID**’ being assigned to non-unique fields.

#### Feature Overview

1. As part of this feature, a validation will be performed to verify whether the ‘**lookup key**’ is available in the destination Org.
2. A verification will be performed to confirm whether users have access to the ‘**External ID**’.
3. If the external unique ID is changed to a ‘**non-unique field**’ (example: Name), then a notification will appear when users click on the ‘**Create Dataset & Deploy**’ or ‘**Create Dataset Commit & Deploy**’ button.

#### Step-by-Step Guide

1. Select the required values from the dropdown available on the ‘**Feature Deployment**’ section.
2. If the ‘**external ID**’ is not available, then the following notification as highlighted will be displayed in the popup, when users click on ‘**Create Dataset & Deploy**’, as displayed in the following screenshot.

<figure><img src="/files/bFkDEBgOvRfG683jdeul" alt=""><figcaption></figcaption></figure>


---

# 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://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/ncino/feature-ci-jobs/running-a-ci-job/external-unique-id-validation.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.