1. Help
  2. Orders

Reference field: why duplicate documents are not created

How the order's reference rules out a double entry, and why it locks after the first send.

The problem it solves

A network can drop the connection at the very moment the ERP is writing a document. The service gets no answer. If it simply sent again, the ERP would hold two documents for the same order, and you would find out at the double shipment or at the month’s reconciliation.

How it is solved

Every order writes its reference into a field of the document. The reference is the integration’s prefix and the order number. Before every send, the service searches the ERP for a document with that reference:

  • If there is one, the order is marked “Sent” with the document’s number, and is not sent again.
  • If there is none, it is sent.

So a retry never creates a second document.

Reference field

The document field that holds the reference, for example FINDOC.VARCHAR01. It must be a field that:

  • your business does not already use for something else,
  • accepts a search in SoftOne.

Ask your SoftOne partner which field is free. The format is FINDOC. followed by capital letters, digits or underscores.

Check field

Press “Check field” after you save. The service tries a search on the field. If SoftOne does not accept it, you will see reference_not_filterable and sending is not turned on, because without a search duplicates cannot be ruled out.

Reference prefix

It goes before the order number. Up to 10 letters, digits or hyphens, no spaces, ending in a letter or a hyphen.

Every integration on the same ERP needs its own prefix. Two shops may both have an order numbered 1001, and the prefix is what tells them apart.

Why it locks

After the first send, the reference field and the prefix do not change. If they did, the service would look for the old documents in the wrong field or under the wrong reference, would not find them, and would send them again. The lock is what keeps the promise “never twice”.

If they really must change, write to us before you do anything.

With a partner endpoint

If you send through a partner endpoint, the same check is done by the “check call”. See Partner endpoint.