Hello
I am running this query to check the email attibute for duplication -
IF EXISTS Contacts WHERE (Contacts.EmailAddress = ThisContacts.EmailAddress AND Contacts.ID <> ThisContacts.ID) Then
ThisContacts.Duplicate = 'Yes'
The problem is this is not trapping all the duplicated email addresses. I have just exported the data to excel to check that everytning is working fine and have found another 200 duplicated emails?
Can any one see why this would be happening from the above query!
Thanks
Data Duplication
Graham,
Something has to be different than you described. I just did a quick test BSV copy/pasting your rule into a test bsv & it worked fine.
When creating the second instance of Contacts with a dup email address, AwareIM properly turned Contacts.Duplicate to 'Yes' for the newly added intance. Of course the first one would not have been marked with a Yes until you run the FIND and UPDATE.
Your rule would not detect and fix removing the Yes once a duplicate is resolved.
This rule solved that:
IF EXISTS Contacts WHERE (Contacts.EmailAddress = ThisContacts.EmailAddress AND Contacts.ID <> ThisContacts.ID) Then
Contacts.Duplicate = 'Yes' ELSE Contacts.Duplicate='No'
Note that in the bold area I also removed an unnecessary THIS.
Tom
Something has to be different than you described. I just did a quick test BSV copy/pasting your rule into a test bsv & it worked fine.
When creating the second instance of Contacts with a dup email address, AwareIM properly turned Contacts.Duplicate to 'Yes' for the newly added intance. Of course the first one would not have been marked with a Yes until you run the FIND and UPDATE.
Your rule would not detect and fix removing the Yes once a duplicate is resolved.
This rule solved that:
IF EXISTS Contacts WHERE (Contacts.EmailAddress = ThisContacts.EmailAddress AND Contacts.ID <> ThisContacts.ID) Then
Contacts.Duplicate = 'Yes' ELSE Contacts.Duplicate='No'
Note that in the bold area I also removed an unnecessary THIS.
Tom
Tom
Sorry for the confusion I thought I would just create a Process from scratch to see if this would make any difference. The Rule I have is
FIND ALL Contacts
IF EXISTS Contacts WHERE (Contacts.EmailAddress = ThisContacts.EmailAddress AND Contacts.ID <> ThisContacts.ID) Then
ThisContacts.Duplicate = 'Yes'
Update Contacts
On this I decided to write a process as you described to see if there was any difference!
Sorry for the confusion I thought I would just create a Process from scratch to see if this would make any difference. The Rule I have is
FIND ALL Contacts
IF EXISTS Contacts WHERE (Contacts.EmailAddress = ThisContacts.EmailAddress AND Contacts.ID <> ThisContacts.ID) Then
ThisContacts.Duplicate = 'Yes'
Update Contacts
On this I decided to write a process as you described to see if there was any difference!
Here are the steps:
1) put this rule on the Contacts BO ---- not in your update process:
IF EXISTS Contacts WHERE (Contacts.EmailAddress = ThisContacts.EmailAddress AND Contacts.ID <> ThisContacts.ID) Then
ThisContacts.Duplicate = 'Yes'
2) run a process that includes:
FIND ALL Contacts
UPDATE Contacts
Running #2 will cause all the rules for the Contacts BO to fire.
Tom
1) put this rule on the Contacts BO ---- not in your update process:
IF EXISTS Contacts WHERE (Contacts.EmailAddress = ThisContacts.EmailAddress AND Contacts.ID <> ThisContacts.ID) Then
ThisContacts.Duplicate = 'Yes'
2) run a process that includes:
FIND ALL Contacts
UPDATE Contacts
Running #2 will cause all the rules for the Contacts BO to fire.
Tom
Graham,
There has to be something else going on in your bsv because I've tested this in a sample bsv with the exact rules stated above. Not sure what else to tell you.
When you tried my earlier suggestion to "try to edit and save one that is know to be a duplicate, the logs should show you what's happening", didn't the logs reveal what's going on?
Tom
There has to be something else going on in your bsv because I've tested this in a sample bsv with the exact rules stated above. Not sure what else to tell you.
When you tried my earlier suggestion to "try to edit and save one that is know to be a duplicate, the logs should show you what's happening", didn't the logs reveal what's going on?
Tom