Skip to content
Customers, suppliers and staff are one record · presentation 5 of 5 · for the whole-system operator — you run the books Read the transcript · Back to the series

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another, each with its own player — or read the transcript, which carries the same steps and every word.

Customers, suppliers and staff are one record · presentation 5 of 5

Merging repoints, it does not marry

You can say what entity merging actually does to your data — repoint every reference it can discover, set the losers inactive…

Finding the duplicates

Step 1 — See what the screen offers you

You will know how candidates are found.

Screen capture pending the demo tenant

The Supplier applet, Entity Merging, a group of near-duplicate names with one marked keep as main

Step 2 — Understand what the job actually runs

You will know why this is not a normal update.

Where this step sits
    flowchart TD
  s1["1. See what the screen offers you"]
  s2["2. Understand what the job actually runs"]
  s3["3. Know what that reaches"]
  s4["4. Learn the two things it will…"]
  s5["5. Know what is left behind and…"]
  s6["6. Decide whether to merge this pair"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s2 here;

Step 3 — Know what that reaches

You will know the blast radius.

What this step names
  1. On the generic document header alone it rewrites seventeen columns — the…
  2. The e-invoice buyer and supplier blocks
  3. The sales agent
  4. The reseller
  5. The shipping recipient
  6. More

What discovery misses

Step 4 — Learn the two things it will not do

You will know where to look afterwards.

What this step names
  1. A column that holds an entity reference under a name without the…
  2. Without a declared foreign key
  3. Is invisible to both rules
  4. Keeps pointing at the record you merged away

Step 5 — Know what is left behind and what is recorded

You will know what evidence a merge leaves.

Where this step sits
    flowchart TD
  s1["1. See what the screen offers you"]
  s2["2. Understand what the job actually runs"]
  s3["3. Know what that reaches"]
  s4["4. Learn the two things it will…"]
  s5["5. Know what is left behind and…"]
  s6["6. Decide whether to merge this pair"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s5 here;

Before you press it

Step 6 — Decide whether to merge this pair

You will have a routine.

What you do
  1. Open both records side by side and copy anything the survivor lacks onto the…
  2. Check they are the same kind of thing…
  3. Run it out of hours

NarrationSlide 1 of 10

Left and right arrows, or the space bar, move between slides; f is full screen and Esc leaves it. Clicking the left or right half of a slide pages it. Play and pause belong to you — nothing moves on by itself unless you tick the box above.