Locations¶
The location list (/v2/location) is the grid over all location/loan entries. Every row is a movement of a device (location change or loan) — a device's current location is the entry with the active flag set, see Reservations and Locations.
List view¶
The columns come from the field administration (by default location fields, loan start/end, active flag, customer, status). As in every TableMaster grid, column selection, filters, sorting, export and saved views are available.
Actions¶
| Action | Description | Permission |
|---|---|---|
| New loan / location | Opens the field-configuration-driven form (optionally with availability check) | location_edit |
| Delete (bulk action) | Deletes marked entries; if a device's current entry is deleted, the most recent remaining one is promoted automatically | location_delete |
| Reports | Reports configured for locations (e.g. loan slips) via the report menu | report visibility |
| Double-click | Opens the detail view (/v2/location/[id]) |
location_view |
Detail view¶
Double-clicking a row opens the location entry (/v2/location/[id]). Because a
row is a movement of a device, the page answers first which device this is
about and how the entry currently stands:
- Device line at the top: asset number, manufacturer and model, linked to
the device (only with
inventory_view). - Summary line below it: status, whether this is the device's current location or a historical entry, the period with its duration and time remaining ("26 days, ends in 5 days"; overdue returns in red), and the target in short form. It stays visible when the master data is collapsed.
- Master data: the fields from the field administration, collapsible.
- Target: customer, contact person and delivery address as links — or the internal site, or the free text, depending on what the entry carries. An entry has exactly one target.
Below that, the tabs:
| Tab | Content |
|---|---|
| Standortverlauf | Every movement of the same device, current entry first. From here you jump to the previous or next location. |
| Mitgebucht | The devices booked as one unit together with this one. The tab only appears when such a booking exists. |
| Berichte | The reports configured for locations, e.g. the loan receipt. |
| Verlauf | Who changed which field and when, with readable values instead of internal ids. |
Status of an entry¶
The status is mandatory and says what kind of movement this is. Three values ship with the product:
| Status | Meaning |
|---|---|
| Standort | The device sits at this place, it is not on loan. No loan receipt, no return date. |
| Busy | The device is on loan. Triggers the loan receipt. |
| Reservation | The period is earmarked for a borrower, but the device has not gone out yet. |
Add your own values via Recording statuses,
type location. The shipped values can be renamed — the key is the internal
uID, not the caption.
Existing installations
Until August 2026 only Busy and Reservation shipped. Merely moving a device meant declaring it on loan or reserved. Standort is added by the next migration without touching any status of your own.
Assignment to devices¶
An entry always belongs to exactly one device (inventory_id). New entries are created:
- From the locations grid — "New loan / location", choose the device in the form
- From the inventory detail page — "Locations" tab → loan/return
- From the inventory grid — "Location/Loan" bulk action for several marked devices
Permissions¶
| Permission | Description |
|---|---|
location_view |
View location list and details |
location_edit |
Create and edit entries |
location_delete |
Delete entries |
Your own location values instead of customer selection¶
The location form is built around an external recipient: customer, contact person, delivery customer. If you do not lend out devices but manage them internally, none of that applies. For you a location is a place on your own site: Plant 2, Hall 3, Test bench 14.
No extra module is needed for this. In field management
the Location field (location_2) can be switched from free text to a
curated option list, and the customer fields can be hidden.
Setting it up¶
- Open field management and select the Location table (
location). - On the Location field (
location_2), set the field category to Option list (PickList). - Enter your own places as an option list. The format is
key:label, entries separated by#:
The key is stored, the label is displayed.
4. Hide the fields you do not need: Customer, Contact person,
Delivery customer, Alternative delivery address.
5. Optionally switch Department (location_3) and Station
(location_4) the same way if you need a second level.
From then on the form offers a selection instead of a text field, and the grid filter matches reliably because every row carries the same key.
What this approach cannot do¶
The option list is a string in the field configuration, not a master data record. That comes with limits worth knowing up front:
- No hierarchy. "Plant 2" will not find the devices in "Plant 2 / Hall 3". If you want to report per plant, choose meaningful keys and filter on the leading characters.
- No address on the place. Delivery notes fall back to the tenant address.
- 36 characters for key and value combined.
- Only the label can be renamed safely. Changing a key leaves every existing row showing the old value and dropping out of the selection. Pick stable keys from the start.
- Above roughly 500 distinct values the selection filter degrades back to a free text filter.
For small, flat lists of places this is the right solution. Once the list grows or needs a hierarchy, a proper location catalogue is the way to go.
Migrating from V1
If the option list was maintained in a V1 installation, it currently does not carry over during the migration to V2. The location values themselves arrive in full, but the field starts out as free text again in V2. Re-enter the list once in field management afterwards; existing values are preserved.