Properties / DB Columns

One card for each property or column

Each collapsed card represents one module property. Open a card to configure the database column, form input, validation, lookup behaviour and supported rules. Keep technical names stable and give users a clear label.

• Column name: a stable identifier without spaces or punctuation.
• Data type and length: the database representation, such as varchar, text, date, integer or decimal.
• Input type: the generated control, such as text, select, checkbox, textarea, file, date, HTML or hidden.
• DB field: whether the value is stored in this module table.
• Display in form: whether the field is available to the generated create/edit layout.

Keys, sequencing and financial years

A normal generated table needs one primary key. Incremental numbering is supported only on the module primary key; financial-year document numbering uses its own supported field settings.

• Use a primary key for the record identity.
• Use a unique key only when duplicate business values must be prevented.
• Use financial-year and max-FY behaviour only on compatible fields.
• Do not expose automatic CompanyID or system fields for user entry.

Calculated values

Eligible numeric fields can use structured calculation metadata. Define the target and its source fields so Jhapu can apply the same rule in the browser and on the server.

• Keep the source fields in the form when users must see or enter them.
• Make calculated targets read-only when manual override is not allowed.
• Test create and edit; the server remains authoritative.
• Use voucher amount calculation separately when accounting needs a posting-specific expression.

Basic Update eligibility

Enable Basic Update only for descriptive fields that may be corrected without running the full transaction update. Administrators can later grant a user access to selected eligible fields.

• Supported: safe text, textarea, date, fixed select and checkbox values.
• Not supported: keys, system/workflow fields, lookups, fetched values, calculations, incremental numbers or financial-year fields.
• Basic Update never changes voucher, stock, GST, totals, approval or child rows.

Before leaving this tab

1. 01
   Check identity

   Confirm one primary key and the correct CompanyID behaviour for the module type.

2. 02
   Check required values

   Mandatory fields must also be reachable in the create form or filled automatically.

3. 03
   Check input relevance

   Verify each input type, fixed value list, lookup and read-only setting.

4. 04
   Check safe updates

   Enable Basic Update only where a restricted correction cannot affect business postings.