Extra fields on the shop's own documents
The customer asks: Extra fields on a purchase order and its lines, a goods receipt, a stock transfer, an expense or the till close
- Verdict: Ready, with limits (1)
- Door: Manifest · area: Documents and print › Your own records, fields and buttons
- Recipe: Shipping your own data in a manifest
- Sample: none yet
- Checked: carried 2026-10-16 · not re-run
What you build
A manifest adds fields, named with your prefix, to the shop's own record types and their child tables.
Limits
- A manifest cannot make such a field required, unique or defaulted: use a save rule (the card required-when-another-filled).
Tell the customer
The documents carry the extra fields; a rule that a field must be filled is a separate save rule.
What next
- Tell the customer the 1 limit above, and write it into the proposal.
- Follow the recipe: Shipping your own data in a manifest.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
- Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.
Install it on your sandbox the way the shop's administrator will; the checker refuses a manifest that declares code.
Related needs
- A field must be filled when another field holds a value — Ready, with limits (1)
- Keep each customer's prescriptions in iVendNext — Ready
- Keep our own records, such as a warranty register, in iVendNext with their own screens and print formats — Ready, with limits (1)
- The list of stock counts showing the quantity, the difference and the stock value — Ready, with limits (4)
Start a project shortlist with this need · Put it in your blueprint · Every need