Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I can think of the following approaches to the task (depending on the number of records, repetitiveness of the import, automatization requirement etc.) they may be all good somehow. Would you care to elaborate on the current conditions?</p> <ol> <li><p><strong>Excel.</strong> You could filter out the data using Excel and then, once you've obtained a unique list, import it.</p></li> <li><p><strong>Plugin.</strong> 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></li> <li><p><strong>Workflow.</strong> Run a process removing any instance calculated as a duplicate.</p></li> </ol> <p>You also need to consider the implication of such elimination of data. There's a mathematical issue. Suppose that the uniqueness' radius (i.e. the threshold in this 1D case) is 3. Consider the following set of numbers (it's listed twice, just in different order).</p> <pre><code>1 3 5 7 -&gt; 1 _ 5 _ 3 1 5 7 -&gt; _ 3 _ 7 </code></pre> <p>Are you sure that's the intended result? Under some circumstances, you can even end up with sets of records of different sizes (only depending on the order). I'm a bit curious on <em>why</em> and <em>how</em> the setup came up.</p> <p>Personally, I'd go with plugin, if the above is OK by you. If you need to make sure that some of the unique-ish elements never get omitted, you'd probably best of applying a test algorithm to a backup of the data. However, that may defeat it's purpose.</p> <p>In fact, it sounds so interesting that I might create the solution for you (just to show it can be done) and blog about it. What's the dead-line?</p>
    singulars
    1. This table or related slice is empty.
    1. PODynamic CRM 2011 Import Data Duplication Rules
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKonrad Viltersten
    1. USKonrad Viltersten
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODynamic CRM 2011 Import Data Duplication Rules
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COWow, you update your answer when I also update my question to elaborate your answer, haven't see the text under point 3 when I update my question, let me read it first :D thanks...
      singulars
      1. PO
      1. USAnthony Steven
    2. COYes the above scenario is undesirable, however we can still live with that. Regarding why and how, it is not in my capacity to answer, it's actually a behavior of the legacy system that I need to replicate :) I need to make the mock up of this this friday :) Regarding my concern on the "updated" section about performance, do you have any comment to that? Thanks...
      singulars
      1. PO
      1. USAnthony Steven
    3. COBtw, I accept this as answer, I think I will try the plugin approach, thanks :)
      singulars
      1. PO
      1. USAnthony Steven
 

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