Audit database models, custom fields, decimal accuracy, system parameters, and sequences

Models lists every model with its technical name, description, Type and transient flag. Base Object means defined by module code: the ORM rewrites its definition on every upgrade, and the delete guard is absolute — "Model '…' contains module data and cannot be removed." A form shows the model's fields, its access rights and record rules inline, which apps define it, and a live record count.

The one creative act this screen allows is a Custom Object: its technical name must start with x_, it gets a real database table and an automatic x_name field, and its type, model name and transient flag are frozen forever after. The same rule governs Fields: custom fields start with x_ and are fully editable except their model and type ("Changing the type of a field is not yet supported. Please drop it and create it again!"), while on a base field the only thing an administrator may edit is what is translatable — the Field Label and Field Help. Everything else answers with "Properties of base fields cannot be altered in this manner! Please modify them through Python code, preferably through a custom addon!". A standard WindoorERP database contains essentially no custom models or fields — if you see x_ entries, someone made them deliberately.

Fields Selection lists the choice values of every selection field. Admins may edit a value's label; adding or deleting values on base fields is blocked, and editing the stored value rewrites that column in every existing record — label edits only, unless you know exactly what you are doing.

Model Constraints and ManyToMany Relations are bookkeeping for the upgrade machinery — every column read-only, nothing to configure. Attachments lists every stored file with its owning record, type (File or URL), size and checksum; the file content itself lives in the server's filestore, not in the database table. Logging shows only entries written through the logging model (a server action's log(), for instance) — it is not the server log file. Profiling holds performance traces: an administrator first allows profiling for a limited period through the “Enable profiling for some time” prompt, records a trace from the developer tools, and opens it here as a flame graph; without that step a normal user is told profiling is not enabled on this database.

One row per usage, one Digits value each — this is what rounds quantities and unit prices across the system:

On a WindoorERP database the list reads: Product Unit, Product Price, Discount, Stock Weight, Volume and Percentage Analytic at 2 digits, Payment Terms at 6, and Account at 3. Two things to understand before touching it: monetary amounts round by the currency's rounding, not by this screen; and changing a precision never rewrites existing data — which is exactly why lowering one warns you at length that "changing decimal precisions in a running database is not recommended".

A flat key–value store the whole system reads. Changes take effect on the next request — no restart. A handful worth recognising: web.base.url is the address used in emailed links (it follows the last administrator login unless web.base.url.freeze is set to True); base.login_cooldown_after and base.login_cooldown_duration are the brute-force lockout (after 10 failed logins, block for 60 seconds, by default); database.uuid and database.secret identify and secure the instance — the protected keys can be neither renamed nor deleted.

Every numbered document — quotations, purchase orders, transfers, invoices — draws its number from a sequence here. The form is self-documenting, legend included:

Renumbering rules of thumb: adjust prefixes before go-live; never wind Next Number backwards over numbers already used — the next document collides with an existing one.

Every record a module ships carries an External Identifier (module.name). It is how an upgrade finds "its" record to update. Deleting an identifier does not delete the record — worse, the next upgrade cannot find the record and creates a duplicate, or aborts on a uniqueness rule. Deleting the identifier of a view or menu is the classic way a well-meaning admin breaks an instance. Look, filter, export — do not delete.