Note: This process is the same for both Single-Entity Matching and Across-Entity Matching

This section will allow you to modify and standardise your data via predefined transforms. This data will then be utilised for matching purpose. Within this section you can modify custom transformations at session level.

Test Input Phrase: This section lets you test your applied transforms. Each line will show you the transform output.

In this screenshot, only one transform has been selected which only provides one extra output.

Note: You must input your test phrase on the same line as the group folder.

During the matching process – Data Transformations can alter the way that DQ for Dynamics looks at your data (it does not change the actual data). This is very effective for transforming specific data element purely for the purpose of matching. E.g. in the company name field you may have a record of TrueData Ltd and another record entered as TrueData Plc. In this case the “business element” (Ltd or Plc) may be considered irrelevant so you only wish to match on the core of the word “TrueData”. You would use transformations to “exclude” these elements in this case. See individual transformation categories for a more detailed explanation.

NOTE: Users cannot apply transform rules on the multi select option set.

This allows you to work with delimiters stored within the database. Simply insert the left and right delimiter and select your mode. The screen below allows you to configure transform parameters for a ‘Custom Exclude’:

Custom Exclude Modes (options):

1. Remove between Delimiters
2. Remove Delimiters Only
3. Remove Delimiters and between
4. Remove Outside the Delimiters

This will search for a customised word or phrase and replace it with a custom string. The screen below allows you to configure the transform parameters for ‘Custom Transform’:

This is a flexible feature which allows you to bespoke/tailor a match to cater for the unique nature of each user's data. A list of required transforms can be configured using ‘Category’ & ‘Custom Transform Library Configuration’ screens in 'Custom Settings' option under 'Settings' menu. The screen below allows you to configure transform parameters for ‘Custom Transform Library’:

This is used to eliminate one or more characters from left or right end of the data. The screen below allows you to configure transform parameters for ‘Extract Letter(s)’:

This is used to eliminate a particular part of the name information from the data. The screen below allows you to configure transform parameters for ‘Extract Name’:

Mode:

1. Prefix/Title
2. First Name
3. Middle Name(s)
4. Last Name
5. Suffix/Qualification

This is used to eliminate whole word(s) from left or right end of the data. The screen below allows you to configure transform parameters for ‘Extract Word’:

This is used to eliminate all Vowels, Consonants, Numbers, Punctuation and Other Characters from the data. The screen below allows you to configure transform parameters for ‘Remove Characters’:

Mode:

1. Vowels: A E I O U
2. Consonants: B C D F G H J K L M N P Q R S T V W X Y Z
3. Numbers: 0 1 2 3 4 5 6 7 8 9
4. Punctuation: , . : ; - '
5. Other Characters: ` ! £ $ % ^ & * ( ) _ + = [ { ] } @ # ~ < > ? / | \

This transform will allow you to split a string based on a custom delimiter, you have to option to return the result with or without the specified delimiter.

This is used to Normalise, Exclude, Elaborate or Abbreviate standard elements from your data. The screen below allows you to configure transform parameters for ‘Transform Words’:

For a detailed overview of our data transformations, please see our Transform Guide

This will eliminate any spaces at the beginning and/or at the end of an attribute. There is no screen to configure the transform parameters for ‘Trim String’. You can directly drag and drop the ‘Trim String’ rule for any group and it can be viewed as shown below:

Once the data has been transformed, purely for the purpose of matching, it can then be tokenised by a fuzzy matching algorithm. This can be applied by selecting the ‘Match Key’ drop-down. The 'Match Key' is used to select an algorithm for phonetic match token generation.

The 'Match Key' drop-down will have six choices:

Soundex retains the first letter of the input string to formulate its match token. Soundex removes vowels (a, e, i, o, u) and h and w from the input string. The remaining letters are assigned numbers using a lookup table to produce a token of 4 characters.

This means ‘Cathy’ and ‘Kathy’ will not match as their match tokens begin with a ‘C’ from Cathy and a ‘K’ from Kathy. As such, Soundex does not match well where the start of a word sounds the same but is not the same. Also, due to the numeric substitution it is possible to be shown non-matches (false positive) matches.

DQSoundex overloads Soundex with the advanced capabilities of DQFonetix™. This improves the start of word logic and modifies the first letter(s) of an input string. DQSoundex will de-pluralise and pre-process the start of words to manage variances like ‘C’ to ‘K’ as in 'Cathy' and 'Kathy', as well as ‘Ph’ as in Phonetix to ‘F’ in Fonetix.

Metaphone improves the Soundex algorithm by using information about variations and inconsistencies in English spelling and pronunciation, to produce a more accurate encoding.

This allows you to find more precise matches than the simple Soundex algorithm. Metaphone considers a larger set of character transformations than Soundex and therefore analyses a string phonetically with far more accuracy.

DQMetaphone like DQSoundex is an enhanced Metaphone technology with the advanced capabilities of DQFonetix™. This improves the start of word logic and modifies the first letter(s) of an input string. DQSoundex will de-pluralise and pre-process the start of words to manage variances and improve matching.

In the case shown below (Christopher), Metaphone would have generated three of five names matches. However, after running DQ’s advanced algorithms and advanced logic, DQMetaphone allows ‘Kh’ from 'Khristopher' to match with the ‘Ch’ from 'Christopher'. Thus generating the same match key token.

DQFonetix™ contains our advanced phonetic algorithms developed over the last 25 years by DQ Global. The algorithm is property DQ Global and hence we do not share the specification of the process. However, DQPhonetix™ has four key features:

• Five spoken languages – English, Spanish, French, Italian and German
• Avoids false matches
• Overcomes character variances
• Deals with diacritics

DQPhonetix™ provides your CRM system with the most varied matching window to highlight duplicate matches that may not be picked up – or falsely matches - in Soundex and Metaphone.

Selecting no match key will not generate a phonetic token, hence no match token will be generated. However, this allows you to match identical strings.