- \n
- Paribus 365™ Data Cleansing<\/li>\n
- Microsoft Dynamics 365 CRM<\/li>\n
- Infor CRM SLX (Saleslogix)<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
For the reviewers of Paribus 365™ Data Cleansing\u00a0Match Results having information columns that speed up the decision are important.\u00a0 The information columns displayed are controlled in the Data Set.<\/p>\n
![\"Data](\"\/help\/wp-content\/uploads\/2017\/01\/fig1counts-300x190.png\")
<\/a>Fig. 1<\/figcaption><\/figure>\n As well as adding standard fields the information displayed can be enhanced further.<\/p>\n
Adding Counts<\/h2>\n
When determining which record should be the primary member of a duplicate group, keeping the contact with most history or the account with most contacts is frequently the preference.\u00a0 These types of counts can be exposed in the Information Columns.<\/p>\n
Note:\u00a0 It is also preferable to have the record with the most associated records as the primary member for processing purposes during a merge.<\/p>\n
A SQL statement can be included within the Information column definition to provide a count of associated records.<\/p>\n
An example SQL statement is below:<\/p>\n
(SELECT COUNT (CONTACTID) FROM CONTACT WHERE CONTACT.ACCOUNTID = ACCOUNT.ACCOUNTID) As ‘Number of Contacts’<\/p>\n
The Data Set would appear as example image here.<\/p>\n
![\"Adding](\"\/help\/wp-content\/uploads\/2017\/01\/dr-kb-1.jpg\")
<\/a>Fig. 2<\/figcaption><\/figure>\n Resulting in a more informed view of the potential duplicate.<\/p>\n
![\"Primary](\"\/help\/wp-content\/uploads\/2017\/01\/fig3-counts-300x99.png\")
<\/a>Fig 3<\/figcaption><\/figure>\n <\/p>\n
![\"Data](\"\/help\/wp-content\/uploads\/2017\/01\/fig1counts.png\")
<\/a>