Custom validation to ensure the uniqueness of member names/node and descriptions or aliases

Summary:

The client has requested a custom validation to ensure the uniqueness of member names, node names and descriptions or aliases.

Example: Member Name: 6130000

Description/Alias: Staff Salaries

In this case, we already have a member named Staff Salaries. Therefore, we need to implement a validation that enforces users to use the member name itself as the description/alias if that member/node already exists for any member names.

Content (please ensure you mask any confidential information):

Custom Validation, Constraint

Version (include the version you are using, if applicable):

Code Snippet (add any code snippets that support your topic, if applicable):