NocoDB | 2026.04.0

NocoDB 2026.04.0 released on 13-04-2026


NocoDB 2026.04.0 is out now. Map View turns GeoData fields into interactive map pins, two new identifier fields (UUID and Auto Number) provide stable, database-backed IDs, and Link to Another Record (LTAR V2) rebuilds linked-record behaviour to show display-value pills and a consistent junction-table architecture.

See the release notes on NocoDB’s GitHub or the official docs for setup, upgrade guidance and full details.

What’s in this release

  • Map View — place records as interactive pins from GeoData fields; click pins to view record details and use filters to limit visible pins (use cases: office locations, customer addresses, field service routing, retail networks).
  • New identifier fields — UUID: auto-generated 36-character, read-only identifiers guaranteed unique at the DB level; Auto Number: sequential, gap-free counters for invoices, tickets, orders and similar use cases.
  • Link to Another Record (LTAR V2) — linked values render as display-value pills, use a consistent junction-table architecture, and enable future spreadsheet-like behaviours; new LTAR fields default to V2 and existing links can be upgraded in-place. Legacy Links field type is deprecated.

Upgrade notes

  • Legacy Links is deprecated and cannot be created any more; existing Links continue to work. Plan upgrades to LTAR V2 via the in-place upgrade path in the UI and consult the docs for migration instructions.
  • Linked-record search now matches the display-value field only — ensure any data you need searchable lives in that field. No automatic rollback is provided; if you need to revert, restore from your backups or roll back to the previous release tag on GitHub.

Share feedback or report issues on the project’s GitHub — we’d like to hear how Map View, the new identifier fields or LTAR V2 perform in your bases.

Related posts

Weekly Tech Digest | 06 Jul 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.

wolfCOSE zero-allocation parsing in embedded C

wolfCOSE looks sensible only if you care about what your firmware actually has to carry. I like that, because on small targets the wrong crypto feature can cost more than the message itself, and there...

restic | v0.19.1

restic v0 19 1: safer FUSE mounts and mountpoint checks, robust backup source and exclude handling, clearer CLI JSON output, Windows SFTP deletion fixes