Capabilities

Everything a data team needs to run its screens — nothing it has to build

The capabilities below ship today in the beta-ready release. Items that are still coming are listed separately at the bottom and clearly marked as roadmap.

Dynamic data engine

The heart of the product: a runtime-generated data grid and editor for every configured area.

  • Server-side paged grids over your SQL Server tables — sortable columns, drag & drop column order, numbered pagination with a page-size selector
  • Inline row editing, with every save re-validated server-side; only columns marked editable can be changed
  • Create & delete rows — a New button for new records and per-row Delete, each gated by the group’s permissions
  • Value, Text, Date, Date & Time and Time fields — date fields get native pickers
  • Free-text search across the visible columns — including lookup values
  • An Excel-style filter row — one toggle brings a filter under each column header: unique-value drop-downs with free typing, pure drop-downs for lookups, applied server-side to the whole dataset, not just the visible page
  • Default filters — your administrator defines which rows show by default per screen (nested AND/OR groups, even column-vs-column comparisons, and a TODAY token that resolves to the current date for date fields); users may switch them off for their own session, but never edit them
  • Fail-soft: an unreachable data source degrades that one screen; the rest keeps working
The Guides screen — live data grid with search, an Excel-style filter row, inline editing and pagination
Live data grid — search, filter row, inline editing and pagination

Two ways to enter data — picked per screen

The inline grid is the default. Where a team works on one record at a time, the same screen can be a designed, full-page form instead — and switched back at any time.

  • Designed entry forms as an alternative to inline editing — each screen runs as grid or full-page form, chosen per area
  • Structured sections with per-field labels, placeholders, half-width fields and design elements (captions, separators, spacers) for explanations — designed visually by your administrator, no code
  • Master–detail tabs on the edit form: manage linked rows (e.g. a tour’s options) in the same screen, with auto-detected foreign-key linking
  • Live preview in the designer renders exactly what your users will see — then Save, reset to default or discard
  • Both modes coexist — the inline grid stays available on every screen, whatever you design
The Tours and Tour Stops designed entry form — structured fields, dropdowns and a Tour Stops detail tab
Designed entry form — structured sections and a master–detail tab for the tour’s stops

Lookups & value lists

Meaningful names instead of raw IDs — in the grid and in the editor.

  • ID columns display the meaningful name and become dropdown editors
  • Table-based lookups or a customer-written SQL statement returning key/value pairs
  • Lookups can live on a different server than the data
  • Search works through lookups — searching “Dublin” finds the city’s rows even though the column stores an ID
The lookup editor — data source, table, key and value fields, a SQL mode and a test showing the top records
Lookup definition — table or SQL mode, with a live test of the top records

Multi-server by design

Areas on different SQL Servers and databases coexist side by side in one application. Windows or SQL authentication, TLS options (Optional / Mandatory / Strict), credentials encrypted at rest, and a connection test with a readable result.

Navigation your team understands

A customer-built menu tree — folders and data areas at several levels — with accordion behaviour and per-entry selection highlight. What each group sees is part of the permission model, not a cosmetic setting.

Administration & audit, in-app

Data Sources, Lookups, Areas, Form Designs, Groups, Users and Menu are managed by your administrators inside the application. The area editor auto-detects columns and the primary key, and Refresh Fields re-syncs with the database when the schema moves. System Settings adds a one-click connection health check — every data source and lookup tested, with per-item status and response time — plus version and license information at a glance. A Data Audit log records which user changed which records, giving your team a clear accountability trail.

Permissions that hold

User → single group → area & menu permissions, enforced server-side in the data engine and the navigation — not just hidden in the UI. Administrators bypass; everyone else gets a friendly, multilingual “no access” message.

Six languages, one team

The complete UI — screens, messages and hints — ships in English, Deutsch, Español, Galego, Italiano and Português. Each user’s language is stored in their profile and applied at sign-in. Users can also update their own password, e-mail and language in a self-service profile — no administrator needed.

Safe by design

The application never creates or alters database structures — no DDL, ever. Queries are parameterized, identifiers are whitelist-validated, and the browser never sees data-source credentials. It is a guest in your database, not an owner. And there is no AI anywhere: every result is computed deterministically on your own infrastructure.

Roadmap — not yet available

What comes next

These items are planned and clearly not part of the current release.

  • Roadmap CSV / Excel export of the current view
  • Roadmap Reports, and bulk change across selected rows
  • Roadmap Notifications & data extracts (e-mail based)
  • Roadmap Cloud service with local data (secure bridge) — whitepaper available on request

Want to see these capabilities on your data?

Book a demo and we will configure a screen against a table that looks like yours.