Duplicate accounts - Arabic names
Answered
Description of the issue :When creating a new exhibitor, users search for the exhibitor in the account list. Since exhibitor names are mostly added in Arabic, spelling variations (Let's say sometimes it's written differently from one user to another) cause users to miss existing records and create duplicate accounts with the same details although duplicate checking is enabled
Customer : Kuwait International Fair
Business Impact : Duplicate accounts lead to data inconsistency, difficulty in tracking exhibitors, and extra manual work to correct records.
Current Process (Customer’s Approach) To reduce duplication, the customer adds a corporate ID from the company’s license to each account. They choose the field “ Search”(EV870_ACCT_Master) EV870_Alpha_Search_Key because it can be used to search in the search bar for accounts. They renamed the field and made it mandatory. However, this process does not include any duplicate checking or warning that the corporate ID is already taken.
What would be the best practice and sustainable approach to ensure long-term data quality and prevent duplication? Is there another field that can be used on from the search and have a warning message available?
Thanks!
-
Minka Verkaar can you advise on best practice here
-
I understand the business case. Give me a bit of time to investigate the options to see if I can find anything.
-
Thanks Minka. Can you update here if you come up with anything based on your discussion.
-
Yes, absolutely!
-
Hi Mariam Abid their workaround will never work, since the system will not check other fields than Account Name or Email Address on Account Level, see also the article in the Support Centre:
So even when they search on the Company ID in stead of the Company Name and for some reason they can not find it, the system allows you to create a new Account with the same ID.
It might be a bit of an open door, but if users use different variants, it’s almost impossible for the system to perform a proper duplicate check.
A customized webhook could potentially check if the Company ID field is already in use when they create a new one, but for that I would recommend to move this value to a more standard field like External Code or Fax Number.
It would be an enhancement to add more fields to check when it comes to duplicates. For example; as organization you have the option to add more options, like External Code, combination of Address 1, Address 2, Address 3, Postal Code etc.
Hope this helps.
-
Hi Minka Verkaar ,
Thank you for your feedback. I agree and my thought was this cannot be a maintainable workaround. I believe they use the Search key because it is part of the fields that can be used for the search bar on Accounts. I will share with them your input and see if thy are open to explore the webhook option. Many thanks
-
Hi Minka Verkaar I got a follow up question from the customer :
With the Webhook approach, would users still be able to search by both Company ID and Company Name when adding an exhibitor or an account ? Their goal is to ensure that users can easily find existing records, whether they search by ID or by name, to reduce the risk of creating duplicates.
My understanding is that it wouldn't be an issue but I am not sure how the Webhook would do the check in the background. Is it technically feasible within the current Momentus setup or with the suggested webhook approach?
Thank you!
-
It depends of course how the webhook is being build, but I had in mind the Webhook would only check if the Company ID is already in used when the new record gets created. So this is not related to the search functionality.
-
Thank you for your help Minka! Minka Verkaar
Please sign in to leave a comment.
Comments
9 comments
Date Votes