Banks and reusable business data
Keep structured information your business needs to reuse: equipment checks, reference lists, form responses, or content records. A bank defines the columns; each row holds one record. This Banks tool is separate from financial Banking.
Banks
For example, a dispatcher can track the drain-camera kit before arranging a visit. Inspection equipment checks contains the camera, spare battery, and cable reel, with readiness, battery level, and preparation notes. It is a reference table; changing a row does not update inventory quantities or create a booking.
Create a standard bank
- Open Banks in SRVZr and select Create New Bank.
- Keep Standard selected to define the columns yourself.
- Enter a clear name and a description of how the records will be used.
- Turn Locked bank off for a table you intend to edit by hand. The creation form initially enables it.
- Select Add Column for each field and choose a type.
- Select Create Bank, then choose the new bank in the list.
Our example uses these four columns:
| Column | Type | Example |
|---|---|---|
| Equipment | Text | Inspection camera |
| Ready | Boolean | True |
| Battery percent | Number | 90 |
| Preparation notes | Text | Lens cleaned; spare battery and cable cover packed. |

The schema picker also offers image, date, time, list, JSON, and reference types. The walkthrough verified Text, Boolean, and Number with saved rows; check the input and output requirements of a connected tool before choosing a more specialized type.
Add and review records
- Select the bank, then Add Element.
- Enter the equipment name, choose True or False for readiness, enter the battery level if applicable, and add a useful preparation note.
- Select Add Element to save the row. Submitting an entirely blank form shows Fill in at least one field before adding.
- Add the remaining records. Leave a field blank when it does not apply, such as battery level for a cable reel.
- Reopen the bank after a reload to check the saved values.

The example’s three rows survived a full reload. An edited camera value of 90 and its longer preparation note also remained saved.
Read a complete row
Select a row to open its details panel. The panel shows field names, types, and full values that may be shortened in the table. Use Previous row and Next row to move through the rows in the current search and sort order, or close the panel to return to the full table.

Edit carefully
Select Edit in the row panel, review every field, then select Save changes. Confirm the result in the table or reopen the record.
Current editing limitation: in the reviewed version, saved Boolean and Number values appeared blank in the edit form even though the table and details panel showed them. Re-enter those existing values before saving other changes, or cancel the edit. The walkthrough re-entered readiness and battery level before saving so those values were preserved.
Search, sort, and export
- Search rows searches across the displayed field values. Searching “battery” matched both the spare battery’s name and the camera’s note.
- Select a column heading to sort. The example’s Battery percent column sorted numerically, placing 35 before 90 and the blank value after them.
- Select Export CSV at the bottom of the table to download the bank’s rows and column names.
CSV export includes all rows, including rows hidden by search, and is separate from the table’s visible sort order. The downloaded example contained all three equipment records when only two matched the current search. Inspect the file before using it as a filtered report.
Locking and schema changes
Lock disables the main Add Element and Edit Schema controls; Unlock enables them again. The lock state survived a reload in the walkthrough.
Current lock limitation: row details still allowed an edit form to open, and saving the same existing values succeeded while the bank was locked. Treat this lock as a workspace editing control with a known gap. Use business access permissions to control who can access records; do not rely on the lock to prevent every row update.
Use Edit Schema to review or change columns. Renaming or removing a column can delete the values already stored in it. The reviewed rename attempt displayed a confirmation explaining that values in all three rows would be deleted and that renaming does not move values to the new name. Choose Keep editing to return without applying that change. No column was renamed or deleted in this walkthrough.
Form banks and connected tools
The Forms tab in Create New Bank creates a different kind of bank: choose a form so its fields define the columns, review sign-in requirements, and use Create & Link. The app then uses the bank to collect submissions. A form can feed one bank; check whether it is already linked before creating another. This walkthrough used a Standard bank and did not publish a form or submit a response.
Other tools can select a bank explicitly. For an automation, configure the Bank node and test the expected fields in the Simulator. For a custom app, review its Banks connector access. Creating a bank alone does not connect it to a project, app, map, or website.
Troubleshooting
| What you see | What to check |
|---|---|
| Create Bank is unavailable | Enter a name and at least one column; a Forms bank also needs a selected form. |
| Add Element or Edit Schema is disabled | Check the bank’s lock. Form banks derive their schema from the linked form. |
| A typed value is blank in Edit but visible in the table | Re-enter the existing Boolean or Number value before saving, or cancel. |
| A CSV contains more rows than the search results | Export currently includes the whole bank. |
| A schema rename asks to delete values | Choose Keep editing unless you intend to remove those values; renaming is not a data-preserving move. |
| Another tool shows no records | Select the intended bank, check its fields, and confirm the selected business and access. |
For the surrounding planning task, see Prepare a job follow-up. Use Inventory for stock changes and receiving, and Documents for a reusable written checklist.
Review app access to a bank
Banks can have per-app access and can be owned by an app. Before connecting a snippet, check the intended bank, ownership and permitted operations in its settings. Give the app only the data and actions needed for its job.
After changing a connection, test the actual app's read or write path with suitable records. Seeing a table in your own Banks list does not prove that the app or another team member has the same access. Access enforcement and cross-user behaviour were reviewed in source, not tested with another user in this refresh.