Skip to content
Learn
Presentations P-00000 to P-00999
The code you type is not the code that is stored

The code you type is not the code that is stored

Customers, suppliers and staff are one record · presentation 2 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 2 of 5

The code you type is not the code that is stored

You can predict exactly what BigLedger will store when you type a customer or supplier code…

What happens between typing and saving

Step 1 — Type a code and watch it change

You will know that this field is not stored as typed.

  • Type gadgetsphere kv01 and the record holds GADGETSPHEREKV01
Screen capture pending the demo tenant

Customer Maintenance, the create form, with the Code box holding a value typed in lower case with a space

Step 2 — Leave it blank and get one, once

You will know how a code arrives when you do not supply one.

What you do
  1. Leave the box empty and the backend mints a code for each flag that…

Step 3 — Expect gaps in the numbering

You will stop treating these numbers as a sequence you can audit.

Where this step sits
    flowchart TD
  s1["1. Type a code and watch it…"]
  s2["2. Leave it blank and get one…"]
  s3["3. Expect gaps in the numbering"]
  s4["4. Know what is actually enforced"]
  s5["5. Read the exceptions in your own…"]
  s6["6. Decide what to do about it"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s3 here;

What must be unique

Step 4 — Know what is actually enforced

You will know which duplicate a save will refuse.

What you do
  1. Search the listing with the status filter set to all before you conclude it…

Step 5 — Read the exceptions in your own data

You will be able to spot records that did not come in through a maintenance screen.

Where this step sits
    flowchart TD
  s1["1. Type a code and watch it…"]
  s2["2. Leave it blank and get one…"]
  s3["3. Expect gaps in the numbering"]
  s4["4. Know what is actually enforced"]
  s5["5. Read the exceptions in your own…"]
  s6["6. Decide what to do about it"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s5 here;

Step 6 — Decide what to do about it

You will know how to work with the rule instead of against it.

Where this step sits
    flowchart TD
  s1["1. Type a code and watch it…"]
  s2["2. Leave it blank and get one…"]
  s3["3. Expect gaps in the numbering"]
  s4["4. Know what is actually enforced"]
  s5["5. Read the exceptions in your own…"]
  s6["6. Decide what to do about it"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s6 here;

NarrationSlide 1 of 9

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.

Last updated on
One table, four ticks — transcriptThe code you type is not the code that is stored — transcript