Lesson 3 — "Value Registry" or "Existing Field"
One column in the catalog decides more than any other: the storage kind. It answers a single question — may I type a value on this row — and getting it wrong is the most common way to lose twenty minutes with this module. The learner who misreads it goes hunting a form for a box that does not exist, then reports a bug against software that is behaving exactly as documented.
The mental model: the row tells you where to type. Only rows marked Value Registry accept a value here. Rows marked Existing Field are pure documentation; their value lives on the field named in the row, and you open that record or module to edit it. There is no third case and no exception, which makes this the one rule in the course worth memorising.
The click path. Open the catalog and group by storage kind. You get two groups, and they are two different to-do lists. The Value Registry group is your data-entry list, and Lesson 4 walks it. The Existing Field group is a directory: for each row, the field name in it tells you where to go and what to open.
| The row says | What that row is | Where the value is typed |
|---|---|---|
| Value Registry | Storage as well as documentation | Here — on the company's UAE Registrations & Identifiers list, or on All Identifiers |
| Existing Field | Documentation of a field that already exists | There — on the field the row names, in the record or module that owns it |
Why it is built this way. The module documents where each identifier already lives rather than duplicating it, because two fields holding the same number is how a database starts disagreeing with itself. The registry exists only for the identifiers that have no home at all — a small set, and one the module keeps small on purpose. Every row it does not store is a row it cannot get out of step with the rest of the suite.
Worked example. The HR administrator at Marina Ridge Trading LLC looks up Emirates ID Number, sees Existing Field and the core field name beside it, closes the catalog and goes to the employee's form. The finance manager looks up the Corporate Tax registration number, sees Value Registry, and stays where they are. Same catalog, same afternoon, two different destinations — and neither of them had to ask anybody.
The failure mode. "Can I store a value for any catalog row?" No. Only rows marked Value Registry accept a value here; Existing Field rows are documentation, and their value lives on the field named in the row. If you are looking at a row and there is nowhere to type, read the storage kind before you read anything else.