🚀 NocoDB : Feature Release

Availability

| Feature | CE / Free | Paid / Enterprise |
|---|:---:|:---:|
| Multi-Column Field Layout in Forms | ❌ | ✅ |
| Custom Display Value on Linked Records | ❌ | ✅ |
| Multi-Field Link Picker Search | ✅ | ✅ |

Multi-Column Field Layout in Forms

Multi-Column Field Layout is available on the Plus plan and above on Cloud, and with Enterprise license on self-hosted.

Multi-Column Field Layout lets you group related fields side-by-side in equal-width columns. Put first and last name on the same line, fit city, state, and zip into a single address block, or group any inputs that belong together, up to 5 fields per row.

To group fields, drag a field card onto another field's row in the form builder. Both snap to equal width and share the row. Long Text, Attachment, and JSON fields always occupy a full row, since their inputs are too tall or wide to share.

Your layout carries through to the shared form URL. On desktop, fields render exactly as configured; on mobile (under 768 px), rows collapse to a single column for readability.

Learn more about Multi-Column Field Layout →

Custom Display Value on Linked Records

Custom Display Value is available on the Plus plan and above on Cloud, and with Enterprise license on self-hosted.

Custom Display Value lets you override the default on any Link to Another Record (LTAR) field, on a per-link basis. Pick the column that makes the most sense for that link: an email on Tasks → Owner, an external ID on Deals → Account, a tier on Tickets → Customer.

Your choice applies everywhere a linked record appears: cell pills in grid, gallery, and kanban; the link picker dropdown; expanded forms; calendar and timeline inline cards; map view tooltips; audit log entries for link and unlink events; and references in search, filter, sort, group-by, and formula. The setting is preserved across export, import, and base duplication.

Learn more about Custom Display Value →

Multi-Field Link Picker Search, Restored

The link picker dropdown search now matches across multiple fields again. In 2026.04.0, search was scoped to the display value column only for reliability. With this release, broader field search returns, and the dropdown uses virtual scrolling with a chunked cache so it stays smooth on tables with thousands of linked records. Available across all plans.

Improvements and Fixes

• Timeline View now updates in realtime - Bars added, moved, or resized by another collaborator appear on your Timeline immediately, without a page refresh.
• NocoDocs search and replace on large documents - Fixed a freeze and out-of-memory crash that could occur when searching or running replace-all in long documents.
• User cells in shared and public views - User fields now expose only the name and avatar on shared and public views. Email addresses are no longer included in the cell payload.
• Form show-on-condition for V2 LTAR fields - Conditional show/hide rules on form fields now evaluate against the linked record's display value for V2 Link to Another Record fields, matching how the rule reads in the form builder.
• Form view hides AutoNumber and UUID fields - Auto-generated identifier fields are now hidden in the Form fields panel, since they cannot be set by the form submitter.
• Snapshot creation and restore - Fixed a missing date import that broke snapshot creation from base settings, tightened snapshot-name validation so snapshots restore cleanly, and the snapshot restore flow now sanitises derived base titles automatically.

What's Changed

• chore: lint by @DarkPhoenix2704 in https://github.com/nocodb/nocodb/pull/13756
• Nc fix(nocodb): match V2 oo links via fk_mm swap in getRelatedLinksColumn by @rameshmane7218 in https://github.com/nocodb/nocodb/pull/13752
• fix: preserve timezone info in DateTime select for group-by lookup headers by @rameshmane7218 in https://github.com/nocodb/nocodb/pull/13757
• Nc feat: custom display value field for LTAR columns by @rameshmane7218 in https://github.com/nocodb/nocodb/pull/13590
• fix: badge handling by @mertmit in https://github.com/nocodb/nocodb/pull/13773
• Nc fix(nc-gui): evaluate form show-on-condition against display value for V2 LTAR by @rameshmane7218 in https://github.com/nocodb/nocodb/pull/13754
• Nc fix/search by @dstala in https://github.com/nocodb/nocodb/pull/13784

Issues closed

• [closed] V1→V2 Link upgrade: multiple breaking bugs force self-hosted build #13780
• [closed] 🐛 Bug: Some images uploaded as attachments did not generate thumbnails. #13769
• [closed] 🐛 Bug: "Row moved" notification appears when editing non-group fields in the Empty group #13760
• [closed] 🐛 Bug: Group By DateTime field shows group headers with wrong timezone offset (+8h mismatch) #13755
• [closed] 🐛 Bug: Form view "Show on conditions" does not evaluate linked record fields correctly #13748
• [closed] PATCH /api/v1/db/meta/columns/{id} silently ignores new colOptions entries when column already has options #13575
• [closed] 🐛 Bug: filtering does not work on lookup fields #13552
• [closed] 🐛 Bug: Multi select "Alphabetize" miss some when we have many choice #13539
• [closed] 🐛 Bug: [Self-hosted] Unable to download files from attachment fields from Base V3 #12943
• [closed] 🔦 Feature: User-type field default "Me" #10915
• [closed] 🔦 Feature: Edit the size limit to import bigger excel files #5858

Full Changelog: https://github.com/nocodb/nocodb/compare/2026.04.5...2026.05.0

🚀 NocoDB : Feature Release

PostgreSQL ENUM Support

PostgreSQL ENUM columns from external Postgres sources now show up as SingleSelect fields inside NocoDB. One of the most upvoted requests from the community (#4862), this closes a long-standing gap for teams who connect NocoDB to a Postgres database where ENUMs already define the allowed values.

Whether you're connecting NocoDB to an existing Postgres schema where ENUMs are the source of truth, building a hybrid stack where your application writes ENUM values and your team edits them in NocoDB, or simply wanting to enforce a fixed set of values closer to the data, ENUM columns now appear as proper select fields in NocoDB. Reads, writes, and round-trips stay type-safe, and the full set of allowed values is preserved end-to-end.

What's supported

• Read ENUM columns from any connected Postgres source — they appear as SingleSelect fields with the database's labels as options.
• Edit ENUM values from grid, gallery, kanban, and expanded record views; the dropdown is restricted to the column's defined labels.
• Add, rename, and remove options from inside NocoDB — changes apply directly to the underlying Postgres ENUM type.
• When the same ENUM type is shared by multiple columns, NocoDB safely forks a new type for the column being edited so changes don't leak to other columns using the same ENUM.
• Filter, sort, group, and search ENUM fields exactly like any other SingleSelect.

Note: PostgreSQL ENUMs map to SingleSelect only in this release. ENUM array columns and MultiSelect-backed ENUMs are not yet supported.

Improvements and Fixes

• Faster base load on large schemas - Bases with hundreds of tables now open noticeably faster, with table metadata streamed in as you scroll the sidebar.
• CSV export honours active filters - Fixed an issue where exporting a filtered view would occasionally include rows hidden by the active filter set. Exports now match exactly what the view shows.
• Shared Kanban views - Fixed an issue where shared Kanban views would fail to load when the stack-by column was hidden in the view.

Issues closed

• [closed] Shared Kanban view fails to load when the group-by (stack-by) column is hidden in the view #13732
• [closed] 🔦 Feature: Support for Right-to-Left (RTL) text direction in NocoDocs #13617
• [closed] 🐛 Bug: APIv3 returns only 5 linked records in one-to-many field #13616
• [closed] 🐛 Bug: Owner unable to send invitations to new members #13611
• [closed] 🐛 Bug: pnpm bootstrap fails with TypeScript error -Property 'delete' does not exist on dbTableFilter in filterUtils.ts #13602
• [closed] 🐛 Bug: Dragging records in Calendar Month View sets date to the first day of the week #13593
• [closed] 🐛 Bug: Сell of UUID type (read only) can be cleared #13588
• [closed] 🐛 Bug/Feature: JSON export is incomplete and unusable as a database template #13493
• [closed] 🔦 Feature: add autocomplete in Forms input fields #5913

Issues closed

• [closed] Bug: All records invisible after update to 2026.04.2 (SQLite) #13596
• [closed] 🐛 Bug: [Self-hosted] Segmentation fault during startup with v2026.04.0 on arm64 #13526

What's Changed

• fix(ai): use correct activeProjectId in callAiSchemaApi by @rakshith1928 in https://github.com/nocodb/nocodb/pull/13587
• fix: background migration for sqlite by @DarkPhoenix2704 in https://github.com/nocodb/nocodb/pull/13597
• Fix License link in README.md by @Dialga in https://github.com/nocodb/nocodb/pull/13598

New Contributors

• @rakshith1928 made their first contribution in https://github.com/nocodb/nocodb/pull/13587
• @Dialga made their first contribution in https://github.com/nocodb/nocodb/pull/13598

Full Changelog: https://github.com/nocodb/nocodb/compare/2026.04.2...2026.04.3

🚀 NocoDB : Feature Release

Noco Docs

NocoDocs is a full-featured document editor built directly into your NocoDB base. Whether you're maintaining an internal wiki, writing product requirements alongside your feature tracker, documenting onboarding processes, or building a client-facing knowledge base, NocoDocs keeps your documentation right next to the data it references.

• Rich editing: Headings, code blocks, callouts, tables, images, file attachments, embeds, math expressions, and a slash command palette for rapid block insertion
• Real-time collaboration: Threaded discussions to loop in teammates without leaving the document
• Hierarchical organisation: Drag-and-drop document tree to structure your knowledge base with nested pages
• Auto-save: Every change is saved automatically as you type, so you never lose work
• Export anywhere: Markdown or HTML with a single click

👉 Learn more about NocoDocs →

Editors Can Now Manage Views

We heard you loud and clear. This change is a direct response to what our community explicitly asked us to bring back, and we're glad to see it return.

The Editor role now covers the full lifecycle of collaborative views, so routine layout work no longer has to route through a Creator or Owner. Whether your analysts need to tweak filters for a weekly review, your sales team wants to duplicate a pipeline view for a new region, or any teammate wants to drop a sort into a shared view, Editors can handle it directly.

Learn more about collaborative, personal, and locked views →

What Editors can now do

• Create, rename, duplicate, delete, and configure collaborative views (filter, sort, group-by, and so on).

What still requires Creator or Owner (unchanged)

• Lock or unlock a view.
• Modify or delete a locked view.

Role Changes at a Glance

The actions below now have a lower minimum role. "Creator+" means Creator or Owner; "Editor+" means Editor, Creator, or Owner.

| Action | Minimum role (before) | Minimum role (now) |
|---|:---:|:---:|
| Manage collaborative views (create, rename, duplicate, delete, convert, or edit filter, sort, group-by, and so on) | Creator+ | Editor+ |

Improvements

• User field default set to Current User - User fields can now use Current User as their default value, so every new record is automatically assigned to whoever creates it, no manual picker needed.
• Rollup precision for Currency fields - Fixed an issue where the precision (decimal places) option was not visible when a Rollup targeted a Currency field. Decimal formatting can be configured again.
• Comment count on grouped views - Fixed an issue where the comment count indicator did not render correctly when a view was grouped. Counts now appear on each record as expected.

Issues closed

• [closed] 🐛 Bug: just reformating multiline fields from small to capital letter errors #13563
• [closed] 🐛 Bug: "Link to another record" creates unexpected _nc_m2m_* table in UI in v2026.04.1 #13540
• [closed] 🐛 Bug: Init Project error #13534
• [closed] 🐛 Bug: Make single/multi - select colors better #13532
• [closed] 🐛 Bug: Select field option color is displayed incorrectly in v2026.04.0 #13514
• [closed] Bug: Comment count badge disappears on page refresh and missing in grouped view #13062
• [🔦 Type: Feature][👮 Scope : Auth] 🔦 Feature: Two factor authentication (2FA) #2731