# Removing the Account & Contact validation on the Case form

<figure><img src="https://4233060750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhtQupP7ACZVtv3cCNCr%2Fuploads%2Fw6yttKsAQXTHqc4eWoZN%2FCase_Contact_not_belong_Account.png?alt=media&#x26;token=61b8dbd2-b7c3-428f-a7dc-a8b33abff731" 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="https://4233060750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhtQupP7ACZVtv3cCNCr%2Fuploads%2F2KFNXeKpXEU0kdL8jiJR%2FVariables.png?alt=media&#x26;token=1698f132-98a0-4a7e-821b-fb4cc2939efb" 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="https://4233060750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhtQupP7ACZVtv3cCNCr%2Fuploads%2F9IuZVLgn9QGVg1kWccxR%2FUpda_Value_Variables.png?alt=media&#x26;token=4a369e5e-eb60-4b82-9bd9-1664c573697c" 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="https://4233060750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhtQupP7ACZVtv3cCNCr%2Fuploads%2F4CKhzY47XC3UA2rTIole%2FCreated_Case_after_update_var.jpeg?alt=media&#x26;token=7c6a29de-55ae-4720-a671-edc3958cdc6e" alt=""><figcaption><p>Case record</p></figcaption></figure>

Checking with the GIF image...

<figure><img src="https://4233060750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjhtQupP7ACZVtv3cCNCr%2Fuploads%2FNSNjpiNqBx2F0jyEdtj6%2FGIF-Testing-CreateCase-afterUpdateVar.gif?alt=media&#x26;token=ec8ecd34-6b81-457d-a816-ec790372a267" 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**