Current State:

The email attribute is case-sensitive. Therefore, if the same email address is added with a letter (in upper case), it is considered as another value and causes duplication. 

Especially when importing Assets from various sources, it is difficult to adjust the lower/upper case for the email value in the source system/file. Post-import, if the email attribute is set as "unique constraint", it creates a new object which is not ideal for managing objects.

Please note that in most use cases of the email field, it is considered a case-insensitive value.

Proposed Future State:

Allow the email attribute to be case-insensitive to avoid object duplication.

Alternative (e.g. Third Party Plugin):

• Do not use email as a unique attribute.
• Before importing, check and ensure we pass on the attribute value in a case-sensitive manner. 
  • For CSV, use  "=LOWER(A2)" Formula, where A2 is the first cell of the email column