Databases
StackOverflow2013
Postsdbo
PODynamic CRM 2011 Import Data Duplication Rules
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODynamic CRM 2011 Import Data Duplication Rules
    primarykey
    data
    text
    <p>I have a requirement in which I need to import data from excel (CSV) to Dynamic CRM regularly. </p> <p>Instead of using some simple Data Duplication Rules, I need to implement a <strong>point system</strong> to determine whether a data is considered duplicate or not. </p> <p>Let me give an example. For example these are the particular rules for Import:</p> <ol> <li>First Name, exact match, 10 pts</li> <li>Last Name, exact match, 15 pts</li> <li>Email, exact match, 20 pts</li> <li>Mobile Phone, exact match, 5 pts</li> </ol> <p>And then the Threshold value => 19 pts</p> <p>Now, if a record have <strong>First Name</strong> and <strong>Last Name</strong> matched with an old record in the entity, the points will be 25 pts, which is higher than the threshold (19 pts), therefore the data is considered as <strong>Duplicate</strong></p> <p>If, for example, the particular record only have same <strong>First Name</strong> and <strong>Mobile Phone</strong>, the points will be 15 pts, which is lower than the threshold and thus considered as <strong>Non-Duplicate</strong></p> <p>What is the best approach to achieve this requirement? Is it possible to utilize the default functionality of <strong>Import Data</strong> in the MS CRM? Is there any 3rd party Add-on that answer my requirement above?</p> <p>Thank you for all the help. </p> <p>Updated</p> <p>Hi Konrad, thank you for your suggestions, let me elaborate here:</p> <blockquote> <p>Excel. You could filter out the data using Excel and then, once you've obtained a unique list, import it.</p> </blockquote> <p>Nice one but I don't think it is really workable in my case, the data will be coming regularly from client in moderate numbers (hundreds to thousands). Typically client won't check about the duplication on the data.</p> <blockquote> <p>Workflow. Run a process removing any instance calculated as a duplicate.</p> </blockquote> <p>Workflow is a good idea, however since it is being processed asynchronously, my concern is the user in some cases may already do some update/changes to the data inserted, before the workflow finish working.. therefore creating some data inconsistency or at the very least confusing user experience</p> <blockquote> <p>Plugin. On every creation of a new record, you'd check if it's to be regarded as duplicate-ish and cancel it's creation (or mark for removal).</p> </blockquote> <p>I like this approach. So I just import like usual (for example, to contact entity), but I already have a plugin in place that getting triggered every time a record is created, the plugin will check whether the record is duplicat-ish or not and took necessary action. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAnthony Steven
    1. USAnthony Steven
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODynamic CRM 2011 Import Data Duplication Rules
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODynamic CRM 2011 Import Data Duplication Rules
      1. This table or related slice is empty.
      1. VTUpMod
    1. COOK, if we're talking 10^6 records, you **will** need to consider the performance issue. You can set the plugin as async (but that can create other issues). Also, after consulting with my colleague I realize that my suggestion, while 100% correct, is very generic. I assumed that you'd have more fields and a more sophisticated definition of unique-ish-ness. But if you're entirely sure that you'll keep this particular rule set, you might want to go with the pragmatic approach of three duplication detection rules as suggested by Rickard. WHat's your budget for this case? Any?
      singulars
      1. PODynamic CRM 2011 Import Data Duplication Rules
      1. USKonrad Viltersten
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload