and more in a single search tool across platforms. Read the announcement here. |
01/29/2024 09:33 PM
Hi Team,
I would like to inquire about the feasibility of checking email uniqueness while generating an email address via a preprocessor. The requirement is as follows:
Is it possible to achieve this functionality using a preprocessor? If so, could you please provide a sample query or guidance on how to implement this?
NOTE: We are not using Email generation rule in Global configuration because uniqueness of the email is not evaluated as expected.
Expected behavior: For example, if there are two users with the same first and last name but different domains, the expectation is that email uniqueness should also be checked for the first part of the email before @domain.com.
USERNAME | FIRSTNAME | LASTNAME | |
Uniqueness | Domain | ||
90109957 | Uniqueness | Domain |
Current application behavior: In the case of users with the same first name and last name but different domains, the email is generated with uniqueness based on the domain.
USERNAME | FIRSTNAME | LASTNAME | |
Uniqueness | Domain | ||
90109957 | Uniqueness | Domain |
Here, expectation is that for user 90109957, email should be generated as systemusername@xyz.com as there an email already generated with taking first and lastname (uniqueness.domain).
Thanks.
01/30/2024 04:33 AM
Hi @Sanjeevini
From the user preprocessor query you wont be able to check the uniqueness of the email.
Use the Email generation rule and use the user attributes table to store the email address without domain so that you can achieve your use case.
Please check the below post on how you can store the email in the user attributes.
Thanks
Darshan