> For the complete documentation index, see [llms.txt](https://dyns.ntd.asia/power-dynamics/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dyns.ntd.asia/power-dynamics/d365-ce/customer-experience/removing-the-account-and-contact-validation-on-the-case-form.md).

# Removing the Account & Contact validation on the Case form

<figure><img src="/files/MYlXudwa8beo3hTQQ8be" alt=""><figcaption><p>Invalid Contact - error dialog</p></figcaption></figure>

{% hint style="danger" %}
**Invalid Contact**\
The specified contact doesn't belong to the account selected as the customer. Specify a contact that belongs to the selected account, and then try again.
{% endhint %}

Ciao friends,&#x20;

Nowadays, I'm working on the D365 Customer Service for the new project. I've provided the client with case lifecycle management, as well as case creation from multiple channels.

I encountered a Contact and Account validation feature, as shown in the image above. \ <mark style="background-color:green;">**In my situation**</mark>, the user needs to create a case for a new account and a new contact. At this point, the account and contact do not have any relationship since they are both new entries in the D365 Customer Service system.

I wonder why Microsoft requires this relationship validation and how I can disable this <mark style="background-color:blue;">**"functionality"**</mark>.

Okay... ignore the reason why, and I just want to disable this functionality. :smirk:

{% stepper %}
{% step %}

### Find the variable "Customer Entities Relationship For Incidents"

Go to the **Default solution**, then select the component **Environment Variables.** Using the Search box to find the variable **"Customer Entities  Relationshi\[ For Incidents"** easily.

<figure><img src="/files/kXWNdheI76wMWAsC68xG" alt=""><figcaption><p>Customer Entities Relationship For Incidents</p></figcaption></figure>
{% endstep %}

{% step %}

### Edit the Value for the variable

After finding the variable, click to open then click to button **<+New Value>** to override the default value of this environment variable.

<figure><img src="/files/fng15LMDBQxGfN9cjgWb" alt=""><figcaption><p>Add New value</p></figcaption></figure>

Then click **Save** to update the new value <mark style="background-color:green;">**(value = 0)**</mark>
{% endstep %}

{% step %}

### Testing...

I go to my D365 Customer Service Hub and succeed in creating a Case for Account (**A. Datum Corporation**) and Contact (**Kenvin**) as the initial feature image.

<figure><img src="/files/QDksaQeqwfQrWLjli3L6" alt=""><figcaption><p>Case record</p></figcaption></figure>

Checking with the GIF image...

<figure><img src="/files/0iZFTV9bkUoo5z2yE3Jp" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

My client has the same question as me. The reason why... :smile: I just smile and configure to bypass the validation. Funny. :man\_running:

Okay... Hoping well! and Thank you for your reading. \
\&#xNAN;**\[NTD]yns.Asia**