Search the Delivery Note register
Follow this guide to use the live client-side search across the rows already loaded by the register. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Delivery Note → Search delivery notes
What you’ll accomplish
Use the live client-side search across the rows already loaded by the register. This guide follows the supplied Delivery Note module’s live hooks, controller actions, model rules, views and stored side effects.
Follow these steps
- Go to the register.
- Enter a reference, invoice value, recipient, date, status or created-date fragment in Search delivery notes.
- Check the matching loaded rows.
- Clear the search to restore all loaded rows.
Fields and options to review
- Search scans the visible text of each loaded table row
- No server request is made for each search term
- Search scope is limited to the newest 100 records returned by the model
Rules the system enforces
- The search is case-insensitive client-side behaviour.
- It cannot find a record that was not in the initial 100-row response.
- Page-size and search work together on the current loaded set.
How to confirm it worked
- The register narrows immediately to rows containing the entered text.
Safety checks and troubleshooting
- Use the exact reference where possible to avoid selecting a similarly named recipient.
Stay within the supported flowDo not force database values, expose secure tokens, bypass permission checks, replace a stored signature or invent a status or interface that the supplied code does not implement.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.