Duplicate Detection Settings in wMobile (Contacts)

by Fred Block on October 19, 2016

This post has recently been updated for wMobile version 3.1.4.742. The new version can be read on the wMobile Blog.

In the world of information that we live in today, and especially in our CRM products, duplication is often frowned upon. After all, duplication can create ambiguity. Many software packages recognize the potential for duplicate records finding their way into our databases and provide us tools for merging and/or removing the unwanted "extras." This article isn't about how duplicates get into our systems or how to eradicate them if they exist, but it is about a handful of settings in wMobile Manager Console allowing for some control over handling duplication up front.

When creating new or editing existing contact record, wMobile provides control over duplication, allowing duplicates in without warning, or informing the user before the duplication is made in your database.

Accessing the wMobile Manager Console System Settings

wMobile system wide settings are configured from within the wMobile Manager Console. On the wMobile server, this tool can be started from the Windows Start menu. The System Settings are accessed by selecting the wMobile node in the wMobile Explorer window and then double-clicking the System Settings icon.

The settings discussed here are in the "Common" section and will affect both wMobile Phone and wMobile Desktop. To access these specific settings, navigate the tree list as follows:

Configuration > Common > Contacts

The four (4) settings we'll cover in the next sections are:

  • AllowDuplicateEmailAddresses
  • CheckDuplicateContactCriteria
  • DuplicateCriteriaIgnoreBlankValues
  • DuplicateCriteriaIgnoreRecordOwnership

AllowDuplicateEmailAddresses

This setting controls whether duplicate email addresses can be entered into wMobile for separate contacts. This is normally not recommended because email messages are linked based on a matching email address.

Settings are: True or False

  • False = (Recommended) Avoids users from saving duplicate email addresses within the database. With this setting, the user will be warned the email address already exists.
  • True = Allows duplicate email addresses within the database. With this setting, the user will not be warned they're duplicating an email address when the record is saved.

In wMobile Phone, the user will see this message appear:

CheckDuplicateContactCriteria

The desired setting will depend on how the information in your GoldMine database is used. Some companies have a “company-centric” database where each company they work with has a record in GoldMine, and all the contacts they work with are entered as "additional contacts" linked to a company record. Some companies have a “contact-centric” database where they have a separate GoldMine record for each contact they work with. In the latter case, you would not want to be detecting duplicates based on Company, because you’d expect to have multiple records with the same company name. Another consideration is whether you have individual people as customers, where there’s no company name. Detecting duplicates based on Company wouldn’t be very helpful in that case. You’d want to match on Contact, or perhaps Company AND contact, so both would have to match for the new contact to be detected as a potential duplicate. Based on your specific need here is a description of the settings:

Settings are:

  • None – wMobile will not consider records to be duplicated and allow them to be created.
  • Company – wMobile will check only the Company field for duplications.
  • Contact - wMobile will check only Contact field for duplications.
  • Company AND Contact – wMobile will check both the Company field and the Contact field. If "both" of these fields match an existing record, the new one will not be inserted.
  • Company OR Contact – wMobile will check both the Company field and the Contact field. If "either one" of these fields matches an existing record, the new one will not be inserted.

In wMobile Desktop the user will see this message when a duplication warning is presented:

DuplicateCriteriaIgnoreBlankValues

This setting specifies if the contact duplication criteria will take blank values into consideration. The desired setting will depend on how contacts are added in GoldMine. For example, if you have many records where there’s no company name, then you’d want to set this as True to ignore the blank company field.

Settings are: True or False

True = wMobile will check for duplication using criteria from "CheckDuplicateContactCriteria" and "will ignore" records with Company/Contact fields that are empty:

  • CheckDuplicateContactCriteria = Company and DuplicateCriteriaIgnoreBlankValues = True, if a user is trying to insert a new record with the Company field empty and the database has an existing record with the Company field empty, wMobile will not detect this as a duplicate.
  • CheckDuplicateContactCriteria = Company OR Contact and DuplicateCriteriaIgnoreBlankValues = True, if the user trying to insert a new record with the Contact field or the Company field empty and the database has an existing record with the Contact field or the Company field empty, wMobile will not detect this as a duplicate.

False = wMobile will check for duplication using criteria from "CheckDuplicateContactCriteria"and "will not ignore" records with Company/Contact fields that are empty:

  • CheckDuplicateContactCriteria = Company and DuplicateCriteriaIgnoreBlankValues = False, if the user trying to insert a new record with Company field empty and the database has an existing record with Company field empty, wMobile will detect this as a duplicate.
  • CheckDuplicateContactCriteria = Company OR Contact and DuplicateCriteriaIgnoreBlankValues = False, if the user trying to insert a new record with the Contact field or the Company field empty and the database has an existing record with the Contact field or the Company field empty, wMobile will detect this as a duplicate.

In wMobile Phone, the user will see this message appear:

DuplicateCriteriaIgnoreRecordOwnership

This setting controls whether record ownership is honored or ignored when checking for possible duplication.

Settings are: True or False

  • True = wMobile will not take record ownership/curtaining into account for evaluating potential duplicates. This means that if a duplicate exists in the database, a user would be notified of a potential duplicate, even if he or she doesn’t have access to see it.
  • False = This forces wMobile to honor (i.e., not ignore) record ownership/curtaining. If a user adds a record that already exists, he or she will not get any warning of a potential duplicate.

wMobile will take record ownership/curtaining into account for evaluating potential duplicates. This means that if a duplicate exists in the database, a user would not be notified of a potential duplicate because they do not have rights to access that record.

In wMobile Desktop the user will see this message when a duplication warning is presented:

Duplicates in your database: They can be friends or foes... Add the control to wMobile and take charge of how wMobile behaves using these tools available in the System Settings of wMobile Manager Console.

Find similar articles in these categories:

PRODUCT: wMobile

AUDIENCES: Administrators Developers

Fred Block
Application Specialist at UpCurve Cloud
More From This Author »