Hello, I still don't understand how you proceed after clicking the ignore and save button in the video? You created the key, but it gave an error again. And you were able to save it when you changed the e-mail address. Can't we save it with the same e-mail address after ignoring it?
Thanks for sharing your questions. Please find th answers below: 1. In the first case, the duplicate detection rule used is Out-of-the-Box (OOB), allowing us to save a record by providing the option to Ignore and Save, without completely restricting saving. 2. In the second implementation, I established a key for the email field, triggering an error only when attempting to enter an email that already exists. After modifying the key field value, it permitted saving the record. Note: Existing OOB duplicate detection rules may already handle duplicate names, addresses, emails, or other fields. If you still have doubts, feel free to email me at manumahaseth0@gmail.com for clarification.
@@powerdynamixx First of all thank you for your answer and effort, I understood properly now. I previously thought that we would fix the error by creating a key. But creating a key is actually an alternative to applying a duplicate detection rule, and it does not allow us to create a duplicate record even if there is no rule. (with error).
Hello, I still don't understand how you proceed after clicking the ignore and save button in the video? You created the key, but it gave an error again. And you were able to save it when you changed the e-mail address. Can't we save it with the same e-mail address after ignoring it?
Thanks for sharing your questions. Please find th answers below:
1. In the first case, the duplicate detection rule used is Out-of-the-Box (OOB), allowing us to save a record by providing the option to Ignore and Save, without completely restricting saving.
2. In the second implementation, I established a key for the email field, triggering an error only when attempting to enter an email that already exists. After modifying the key field value, it permitted saving the record.
Note: Existing OOB duplicate detection rules may already handle duplicate names, addresses, emails, or other fields.
If you still have doubts, feel free to email me at manumahaseth0@gmail.com for clarification.
@@powerdynamixx First of all thank you for your answer and effort, I understood properly now. I previously thought that we would fix the error by creating a key. But creating a key is actually an alternative to applying a duplicate detection rule, and it does not allow us to create a duplicate record even if there is no rule. (with error).
thank you so much ......... keep going 🥰🥰🥰🥰
Appreciate your support.