Release 1.69.7
Release Notes - Seatmap Platform
Version 1.69.7 - 2026-07-30
Release Focus: Hotfix for silent pricing-zone loss — saving a venue schema no longer deletes that schema’s pricing zones and their seat assignments. Delivered as a patch on top of the 1.69 line.
MetaTitle: Release 1.69.7: Pricing Zone Hotfix - Seatmap.pro
MetaDescription: Seatmap 1.69.7 fixes silent pricing-zone loss. Saving a venue schema no longer deletes that schema’s pricing zones or their seat assignments.
What’s Fixed
Saving a schema no longer deletes its pricing zones
PUT /api/seatmap/{schemaId}/ treated the zones list in the payload as the authoritative full set and deleted every stored pricing zone missing from it. The editor manages pricing zones through the separate /api/schemas/{schemaId}/zones/ endpoints and never puts them in the seatmap payload, so an ordinary geometry save arrived with an empty list and wiped the schema’s zones, clearing the pricing-zone reference on every seat and general-admission section.
The loss was silent. It surfaced as “Schema saved, but zones could not be saved. Please try again.” only when a zone assignment was saved in the same session — the assignment then referenced a zone that the save had just removed and was rejected with HTTP 400. In every other case the zones simply disappeared.
An absent or empty zones list now means the request does not manage pricing zones, and the stored zones and their assignments are left untouched. A payload that does send zones keeps the previous full-replace behaviour.
Deleting a zone through DELETE /api/schemas/{schemaId}/zones/{id} still clears the seat and section references first, unchanged.
Reported in production by Envorso. The regression was introduced in 1.65, so any schema saved from the editor since then may have lost its pricing zones; affected schemas need their zones recreated and reassigned.
Issue: SEAT-1109.
Affected products
editor-service— pricing zones preserved when a schema save does not carry them.
Upgrade
No API, configuration or database changes. No integration work is required.