Skip to content

v2.18.0 (2026-07-09)

Overview

Vite Horizon 2.18.0 makes filtering far less guessy: an invalid filter is now refused with the reason, instead of being applied and quietly blanking the layer. It also fixes a layer-list label button that showed the wrong state, and a printing problem where FPP label lines lost their duplicate labels.

Breaking Changes

None in this release.

New Features and Improvements

Filters tell you what is wrong

Previously, a filter with a mistake in it — a mistyped field name, an unclosed quote, a dangling AND — was applied anyway. The layer went blank and all you got was a generic "No Results" message.

Now the filter is checked before it reaches the layer, and if it cannot work you are told why: an unterminated text value, unbalanced brackets, a trailing operator, or the server's own explanation of the problem (often naming the field it does not recognise). Your layer keeps its current filter while you fix it.

See the Filter Tool guide.

Layer list "Enable label" showed the wrong state

For layers served as map images (including the editor and coupe layers), the label action in the layer list always read Enable label, even when labels were already drawing — so the first click switched them off. The action now reflects what is actually on the map.

FPP label lines print with all their labels

FPP "Hide" label lines are now printed by the map service that publishes them, so labels that repeat along a line are kept. Previously the print service re-labelled them with its own rules and silently dropped duplicates, so label lines sharing the same text went missing from the printout.

See the Print Panel guide.

Under the Hood

  • The ArcGIS Maps SDK and several development dependencies were updated to their latest patch releases, verified with an automated boot check.
  • Filter validation is deliberately two-stage: an instant local check for structural mistakes, then a cheap count-only query against the server so its own message can be shown. A network problem is never reported as bad SQL.

Horizon Help Documentation