How prevent Creation of Duplicate Customers

​@lorach 

customization can be implemented in Acumatica to check for duplicate email addresses when a new customer is created. This validation can be configured based on the customer class.

We can also identify how many existing customer records share duplicate email addresses. After reviewing the results, the duplicate records can be validated and cleaned up as needed.

Hi ​@Manikanta Dhulipudi , So, as is, it can’t prevent the duplicate unless there’s a customization?

​@lorach You could look at using the Duplicate Validation if you have CRM but it only works with Leads/Contacts and Business Accounts. You would need to do a customisation to do it on the customer record.

Hi ​@lorach ,

There may be some limitations with the low-code approach; however, we have used it for the following:

User enters Customer Name & clicks [SAVE]
                    │
                    ▼
       RowPersisting event fires
                    │
                    ▼
Does another Customer / Account exist with this Name?
              /           \
            YES            NO
            /               \
           ▼                 ▼
[ABORT & BLOCK SAVE]     [SAVE TO DATABASE]
Show red error on screen: Record is created successfully.
"Customer name already exists!"

Can you try below event-

using PX.Data;
using PX.Objects.AR;
using PX.Objects.CR;

namespace PX.Objects.AR
{
    public class CustomerMaint_Extension : PXGraphExtension<CustomerMaint>
    {
        // Runs right before saving to the database
        protected void _(Events.RowPersisting<Customer> e)
        {
            if (e.Row == null || string.IsNullOrWhiteSpace(e.Row.AcctName)) 
                return;

            // Check if any other account already has this exact name
            BAccount existing = PXSelect<BAccount,
                Where<BAccount.acctName, Equal<Required<BAccount.acctName>>,
                And<BAccount.bAccountID, NotEqual<Required<BAccount.bAccountID>>>>>
                .Select(Base, e.Row.AcctName.Trim(), e.Row.BAccountID);

            if (existing != null)
            {
                // Block save and show error on Customer Name
                e.Cache.RaiseExceptionHandling<Customer.acctName>(
                    e.Row,
                    e.Row.AcctName,
                    new PXSetPropertyException("Customer name already exists on Account: {0}", 
                        PXErrorLevel.RowError, existing.AcctCD));
            }
        }
    }
}

Hope above helps!!

Hi ​@lorach 

You can create Generic Inquiry to check Duplicate without Customization. Check out the ideas on how to do it in the post below.

Best Regards,

NNT

Hi, I’m noticing that on the screen capture you shared, the Create on Entry rule is Allow for the email. If you changed it to Block, could this resolve a part of the problem?

Hi ​@suejohnson10 ,

Thank you for your thorough explanation 🤗. I believe the workarounds you suggested are practical and well thought out, especially the option of having users create business accounts first and subsequently extending them as customer accounts.