Deleting & Why It Can Be Refused
You can delete a location, a facility, an outline or a whole site. Yard Spot refuses a delete when something else still points at what you are removing. The refusal is a safety check: it keeps gates from losing their location and assets from losing their position.
Delete a Location
Open the location's ⋯ menu, choose Delete, and confirm Delete in the dialog.
Delete a Facility
Open the facility's ⋯ menu and choose Delete. The confirmation says what goes with it:
Delete Lot G2 and its 12 locations?
Deleting a facility deletes its locations and its outline (every part, if it has several). If you want to keep the locations, first use Move to the site on each one.
Delete an Outline Not Linked to a Facility
Expand the note at the bottom of the tree that says outlines aren't linked to a facility, and choose Delete outline.
Delete a Site
Choose Delete site next to the Site selector and confirm Delete in the Confirm Site Deletion dialog. The site's facilities, locations and outlines are removed with it.
Deleting Something That Has Gates
When the facility, location or site you delete has gates (active or inactive), the confirmation names them, for example:
North Yard has 1 gate (Main Gate). Deleting North Yard also deletes it.
Confirming deletes those gates first, then the place. You do not have to remove the gates in the Gate Editor beforehand.
When a Delete Is Refused
Yard Spot refuses the change and shows a message at the bottom of the screen. Nothing is deleted: the facility, the locations and the outline all stay as they were.
Cannot remove places that are still in use: gate "North Gate", asset TRL1234 and 2 more
The message lists up to five things that still use the place, then a count of the rest. The things that can hold a place:
| Reference | Why it blocks |
|---|---|
| A gate | The gate's location is the place, or the gate's associated location is. Inactive gates count too, because reactivating a gate must not point at a place that no longer exists. The Location Editor deletes these gates for you when you confirm (see above), so this mainly applies to other ways of deleting, such as the API. |
| An asset | An asset is currently assigned to the place. |
| Appointment configuration | Opening hours, holidays, categories or slot templates are keyed to the facility or location. |
To proceed, clear the reference and try again:
- For a gate, delete it from the Gate Editor, or delete the place in the Location Editor, which deletes its gates for you.
- For an asset, check it out or reassign it.
- For appointment configuration, remove or move the facility's schedule and holidays.
Moving a Location to the Site
Choosing Move to the site on a facility's location keeps its id, so gates and assets that use it still work. Only appointment configuration blocks this, because opening hours and schedules belong to facilities. If that configuration exists, the move is refused with the same kind of message. To turn a whole facility that has only a landing point into a site location, use It's just a point in the setup checklist.
The Same Rule for the API
If you manage sites through the API, the same check applies to POST /site and
DELETE /site/{id}: they answer 409 with the error place_referenced and a references list.
See DELETE /site/{id} and POST /site in the API reference.