A duplicate is a record that Sales is attempting to forward to the server, but can’t. This is because the server data believes that it already contains that same record, so it rejects the Sales program’s attempt to write a “duplicate” entry.

For example, let’s say that Sales has just created a gst_pass number of 1500000. Sales attempts to forward the gst_pass record to the server, but can’t because a record with gst_pass number 1500000 already exists on the server. Sales then displays a duplicate error message.

There are two types of duplicates: “good” and “bad.” A “good” duplicate is a true duplicate: the exact same record – with completely identical fields – does indeed exist in the server data. Because records of this type are relatively easy to fix, they are dubbed “good” duplicates. While they aren’t exactly “good,” they are relatively easy to repair.

A “bad” duplicate is a bit trickier. A bad duplicate means that the local record (the one generated in Sales) is not exactly the same as the record found in the server data. It is a duplicate because the local record and the server record share at least one “primary key” field. Every other field may be different, but at least one “primary key” has lost its uniqueness. Repair of “bad” duplicates usually requires the help of Siriusware Technical Support.