A list column the retailer wants on a record's list
The customer asks: A column the retailer wants on a record's list
- Verdict: Ready, with limits (2)
- Door: Configure · area: Setup and administration › Roles, lists and data rules
- Recipe: 4. Configure first
- Sample: none yet
- Checked: run on a sandbox 2026-10-16 · POS 2.0.0.647 · a list query naming a count's header field difference amount was accepted; not run: choosing the column in the Desk list's own column settings
What you build
The user picks the columns in the list's own settings in iVendNext Desk, or an administrator sets the record type's list settings.
Limits
- Only the record's own fields can be a column; a total of its item rows cannot (the card count-list-totals).
- Picking the column by hand in the list's own settings was not run, so whether a column can be set for every user is not promised.
Tell the customer
Users pick the columns they want on a list; a total of a document's rows is a separate piece of work.
What next
- Tell the customer the 2 limits above, and write them into the proposal.
- Read the chapter: 4. Configure first.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Check it on your sandbox as the people who will use it; where it touches a price or a total, the money kit's release gate proves it (testing and release).
- Make the same settings on the customer's site, from the list you wrote down, through the customer's own change process.
Nothing to code: write down each setting you make on your sandbox, so it is made the same way on the customer's site.
Related needs
- A notification a number of days before a date on a shop's own record, such as a batch's expiry — Ready, with limits (2)
- A statement of what each customer owes, printed and sent on a schedule — Ready, with limits (3)
- Change the limits and who is told in one settings page, not in each rule — Ready, with limits (3)
- Each role sees and does only what it should — Ready, with limits (2)
Start a project shortlist with this need · Put it in your blueprint · Every need