Dulicate Detection does not work correctly while importing data RRS feed

  • Question

  • Hello,

    While importing Data from CSV files we have one rule to detect Accounts that match the following:

    1- Account Name - Same First Characters - 6

    2- Account Name - Exact Match

    3- Web Site - Exact Match

    When importing a list of about 150 rows, we only get 3 accounts as duplicate which is the exact match of existing accounts, but we know that there are about 30 others that are the same first characters with may be a "," or "LLC" at the end.

    How can we fix this,

    Thank you

    Friday, January 18, 2013 1:27 AM

All replies

  • Hi,

    Check this post: https://community.dynamics.com/product/crm/f/117/t/65538.aspx

    Hope this helps.
    If i answered your question, please mark the response as an answer and also vote as helpful.

    Pedro Azevedo Crm Specialist 4.0\2011

    • Proposed as answer by Azevedo PedroMVP Friday, January 18, 2013 1:34 AM
    • Unproposed as answer by Ehamouda Friday, January 18, 2013 1:35 AM
    Friday, January 18, 2013 1:34 AM
  • Azevedo,

    I looked at the link and I am always checking for [if you would like to import duplicates] and make sure it's do not import duplicates.

    it actually detects duplicates but only the Exact Match.

    Friday, January 18, 2013 1:37 AM
  • When multiple conditions are specified, its "AND" operator among them, so in your case, condition 2 is shadowing condition 1 as conditon 2 is always checking for exact match.

    Hope this helps !

    Thanks Satish Reddy http://Learn-Dynamics.com

    • Proposed as answer by Adam Vero Friday, January 18, 2013 10:31 PM
    Friday, January 18, 2013 10:57 AM
  • Hi,

    I am not sure why you have two criterias for Account Name i.e. #1 and #2.  

    Based on your requirement above, remove criteria #2 & #3, it should work. 

    Gopal Kanojiya

    • Proposed as answer by Adam Vero Friday, January 18, 2013 10:29 PM
    Friday, January 18, 2013 11:04 AM
  • As others have pointed out, having two criteria on the same field is unlikely to have the desired effect (I could imagine some edge cases where you want to compare the first few and last few characters, but they would be pretty esoteric).

    To make it easier to see why, you just need to realise that every condition you specify simply sets up a series of fields (or partial fields) to be added to a single string. So if you add a text field with a maximum length of 20 characters, that adds 20 characters, padded with spaces if necessary. Numeric and date fields are converted to text, lookups use the parent record reference.Everything is strung together (concatenated) into a big long string (of maximum length 450 characters).

    This mechanism of building a single long text field means that an indexed search of this is really efficient to do when you add new records, rather than trying to actually compare multiple fields at once.

    So, if you want to check three different fields independently as an "OR", then simply create three rules, and if any one of them is triggered you will get a duplicate record flagged (which would mean on a data import it would be discarded if you choose the setting to not allow duplicates to be created).

    Notice that even this way, there is no point having one rule for the first 6 characters of the Account name and another for the whole of the Account name - clearly if the second one is triggered, the first would be too.

    Hope this helps.
    Adam Vero, Microsoft Certified Trainer | Microsoft Community Contributor 2011
    Blog: Getting IT Right

    Friday, January 18, 2013 10:57 PM