v2.16.0 (2026-06-29)

Overview

Vite Horizon 2.16.0 adds two data-handling features: a Filter Editor dialog — a larger, pop-out workspace for building queries visually or in SQL — and a new Export CSV button in the Feature Table that exports every selected row, not just the first page.

Breaking Changes

None in this release.

New Features and Improvements

Filter Editor Dialog

The Filter Panel gains a launch / pop-out button (brand-blue border) that opens a larger, draggable and resizable Filter Editor. It is non-modal, so the map stays interactive while it's open, and a Source Layer dropdown lets you switch layers without closing it. The dialog has three tabs:

• Visual Builder — build a query without writing SQL. Add conditions (field + operator + value), pick values from a searchable unique-values list, and nest AND/OR groups for logic like (A AND B) OR (C AND D). A Generate SQL button converts your conditions to SQL for review.
• SQL Editor — the full SQL query builder with more room: operator-insert buttons, field insertion, and a unique-values picker.
• Statistics & Export — calculate field statistics (count, sum, average, min, max, std deviation) and export results to Shapefile or KML.

See the Filter Editor Dialog guide.

Feature Table — Export CSV (all selected rows)

A new Export CSV button (next to the selection count) exports every selected row to a single CSV file. The table's built-in "export selection" is capped by the service's record limit (typically ~1,000–2,000 rows), so a "Select all" would previously truncate. The new button fetches the selection in batches and assembles the file in your browser — a Select-All downloads every selected row, however many that is.

• Coded-value fields export as their labels, dates as ISO timestamps, and the file includes a UTF-8 marker so Excel reads accents correctly
• Values are protected against spreadsheet formula injection
• A progress bar with a live count and a Cancel button appear during the export

See the Export CSV guide.

Under the Hood

• Both new query paths validate input to guard against unsafe SQL — numeric comparison values are checked before use, and destructive keywords remain blocked.
• The ArcGIS Maps SDK components were updated to their latest 5.1.x builds.