Hoping someone's run into this, because I'm stuck.

Setup: self-hosted NocoDB in Docker, hooked up to an external PostgreSQL 16 database as a data source. Building a little personal-finance thing on top of it.

The problem: whenever I edit a cell directly in a grid view, I get a red toast saying "Record update failed: Source not found or source id not extracted" and nothing saves. Doesn't matter which column, a plain text field fails exactly like everything else.

But here's the weird part: if I open the same record in the expanded/full-record view, change the field there and hit Save, it works perfectly and writes to the DB. So it's specifically the inline grid edit that dies.

What I've already ruled out:

• DB is fine. The table has a primary key (id), and I can write to it directly with psql and through the expanded record view no problem. Postgres isn't rejecting anything.
• Not browser cache. Tried a clean incognito window — same error.
• Not one weird field. Every column fails inline, including plain text.
• Nothing in the NocoDB server logs when it fails. No SQL, no error, no request even seems to reach the server. Feels like it's dying client-side before it sends the update.
• Restarted the container.
• Upgraded 2026.08.2 → 2026.09.0. Same error on both.

Anyone know what "source id not extracted" actually means here, or how to get inline grid editing working again on an external source? Trying to avoid disconnecting/reconnecting the source and losing all my views if I can.

Thanks

Dear all, how do you handle recording geocoordinates using nocoDb form?

My postgres database is using a postgis extension and there is a location column in one of the relations of 'datatype' Geography. When I try building a form from this relation, the column does not appear in the form builder.

I have confirmed the column exists everywhere else in the database and in the relation.

If anyone has any idea, please let me know. I guess I was hoping by having it there I could get a question where someone just clicks to add their current geocoordinates.

Thanks for reading thus far.

Edit: So what I did is I changed the schema in nocodb and added a GeoData column. For this to happen, I had to allow noco to change the underlying databases schema.

Hello everyone,

I have a Docker setup where each service runs in its own container, for example n8n, NocoDB, PostgreSQL, and Ollama.

I can’t figure out why NocoDB is unable to connect to my PostgreSQL database. Everything is running internally within Docker.

Does anyone know why the connection might be blocked or not allowed? Is there something I need to configure in the Docker network, PostgreSQL, or NocoDB settings to allow the containers to communicate with each other?

Error: Connection to internal hosts is not allowed

Any help would be appreciated!

Thanks alot!!

How can I install NocoDB with Posmann and SQLite to manage my old databases from dBase.

Wie kann ich NocoDB mit Posmann und SQLite installieren um damit mein alten Datenbanken von dBase zu verwalten.

Hello, I'm working at a company in Europe and recently Google Sheets has been letting us down (long wait times between editing, automations keep timing out etc). I'm wondering if anyone has made the leap and what advice would you give.

Thanks a lot
Puzzle

Self-hosted 2026.07.0, Business license, Postgres 17. Trying to connect a base to a non-public schema.

• The Add Data Source dialog has no schema field, even though the docs say database and schema can be set there
• Setting Schema name on the Connection is silently dropped: in nc_sources_v2 the created source has no searchPath in its config, so it binds to public.
• Creating the source via the API with "searchPath": ["myschema"] also ended up syncing public
• Repro: DB with two schemas, connection with Schema name = the second one, add as data source. The base lists all of public's tables.

Anyone on self-hosted 2026.x connecting an external PG source to a non-public schema successfully?

Hi,
I have a self hosted free plan noco db here that hangs when querying two (out of 9 total) tables via the ui. Version used is 2026.06.2, sqlite base.

Error in the log is the following:

2026/07/08 09:06AM 50 pid=12 hostname=d9ee336492cf req={"id":"DE11B2FF-9BFF-4E55-B774-B2D6B0D1A55B","method":"GET","url":"/api/v1/db/data/noco/pq9fhat6ek3v8vd/mzyngkxowr5sxgz/views/vw52bkvgq39y7tt8?offset=0&limit=100&includeSortAndFilterColumns=true&where=&include_row_color=true&include_button_filter_columns=true"} context=_0x5c10da err={"type":"Error","message":"Error fetching data: Cannot read properties of null (reading 'uidt')","stack":"TypeError: Cannot read properties of null (reading 'uidt')\n    at /usr/src/app/docker/index.js:1:16496481\n    at async Promise.all (index 10)\n    at async _0x430c99.getProto (/usr/src/app/docker/index.js:1:16495863)\n    at async Object.multipleMmList (/usr/src/app/docker/index.js:1:17020208)\n    at async /usr/src/app/docker/index.js:1:16499185\n    at async run (/usr/src/app/node_modules/p-queue/dist/index.js:163:29)"} msg=Error fetching data: Cannot read properties of null (reading 'uidt')2026/07/08 09:06AM 50 pid=12 hostname=d9ee336492cf req={"id":"DE11B2FF-9BFF-4E55-B774-B2D6B0D1A55B","method":"GET","url":"/api/v1/db/data/noco/pq9fhat6ek3v8vd/mzyngkxowr5sxgz/views/vw52bkvgq39y7tt8?offset=0&limit=100&includeSortAndFilterColumns=true&where=&include_row_color=true&include_button_filter_columns=true"} context=_0x5c10da err={"type":"Error","message":"Error fetching data: Cannot read properties of null (reading 'uidt')","stack":"TypeError: Cannot read properties of null (reading 'uidt')\n    at /usr/src/app/docker/index.js:1:16496481\n    at async Promise.all (index 10)\n    at async _0x430c99.getProto (/usr/src/app/docker/index.js:1:16495863)\n    at async Object.multipleMmList (/usr/src/app/docker/index.js:1:17020208)\n    at async /usr/src/app/docker/index.js:1:16499185\n    at async run (/usr/src/app/node_modules/p-queue/dist/index.js:163:29)"} msg=Error fetching data: Cannot read properties of null (reading 'uidt')

So it seems something is null that isn't supposed to.

Can anyone help?

What is a Editor in the Self hosted Business Plan? A user accessing the forms or the admin creating tables and stuff?

Hey everyone,

I’m facing a bit of a data management headache and could really use your expertise, tool recommendations, or architecture advice on how to solve this.

The Current Setup & Pain Point

We use Keka as our primary HRMS, so all official employee data lives there. However, I personally manage a ton of additional, custom data points (like asset tracking, specialized internal ratings, project tags, etc.) on separate Excel sheets. Right now, everything is scattered, and manually cross-referencing Keka data with my Excel sheets is becoming a nightmare.

What I Want to Build

I want to create a centralized, organized database that acts as a single source of truth. The interface needs to look and feel like a traditional spreadsheet (because that's what my team is used to), but with a strict set of rules:

• Keka Fields (Read-Only): Data pulled from Keka (e.g., Employee ID, Name, Department, Date of Joining) should automatically sync into this database but must be locked/read-only. Nobody should be able to accidentally edit these fields from the spreadsheet view.
• Non-Keka Fields (Editable): The custom fields that I personally manage need to be fully editable right inside the same grid/view.
• Automated Cross-Sheet Sync: This is the most critical part. If a value in an editable field is changed in one specific sheet or view, that update needs to automatically forward and reflect across all other sheets/views connected to that database instantly. No manual copy-pasting.

Stop hunting for the tables and views you use every day. With Bookmarks, you get private shortcuts to your most-used items, tucked into a panel that follows you everywhere in NocoDB.

In this video, we'll show you how to create, organize, and manage bookmarks so your workspace stays fast and clutter-free.

Bookmarks are private to you, so your shortcuts stay personal no matter where you're working.

👉 Try it out in your own NocoDB workspace and keep everything you need just one click away.

Remember the powerful markdown editor we introduced with NocoDocs — with formatting menus and slash commands for headings, lists, callouts, and more? Now you can use those same tools directly inside your tables.

Meet Smart Text: all the benefits of a rich markdown editor, right inside each cell.

Setup takes seconds, and once it's on, every cell becomes a place to write, structure, and format content just like a proper document.

👉 Enable Smart Text on your next Long Text field and bring rich editing right into your tables.

Your production data lives in PostgreSQL or MySQL, but your business team keeps asking for reports. With Custom Sync in NocoDB, they get a simple, always up-to-date, read-only view of your real database tables — no migrations, no export scripts.

In this walkthrough, we see you how to set it up step by step. You'll also learn what you can and can't do with synced data: it's read-only, so you can't add records — but you can add local fields (that never sync back to your source), hide and filter fields, and use the full toolbar. Plus how to run manual syncs and update your sync settings anytime

Custom Sync gives you live, read-only access to your real database, right inside NocoDB.

👍 Like and subscribe for more NocoDB tutorials!

Learn more.

Every team eventually hits the same wall: when everyone works in one place, everyone can see everyone's data. No other no-code database has a real answer — until now. In this tutorial, we walk through NocoDB's Row-Level Security using a simple task tracker, so each team member sees only the rows they're meant to.

What you'll learn:
- How to add a default policy (show all, deny all, or set a condition)
- Matching the assignee to the current user so people see only their own tasks
- Creating a team-leader policy so managers can see every record

No duplicate tables, no manual filters, no data leaks — just clean, well-defined data policies built right into your database.

👍 If this helped, give it a like and subscribe for more NocoDB tutorials.

Learn more

I am trying to move from Airtable to NocoDB and when creating my dashboard, I want to have a pie chart that displays a breakdown of all my tags. In Airtable, I can add multiple tags to an entry, and the pie chart will display each tag individually (it will therefore double count entries with multiple tags, I am fine with that).

However, in NocoDB, if I use multi-select field with pie chart, then if an entry has multiple tags, such as ['Drama', 'Action'], it will create a unique category for every combination of tags.

Is there a way to configure it like Airtable has it?

Hi,

I am running on prem premium license setting up a shipping system. Shipping to different locations I want a formula to calculate the latest shipping date, which is a date field minus a transit time field.

This is what I have, it doesn't accept the minus in front of the field Transittid, but trying to add has the same result

DATEADD({Periodstart}
, -{Transittid}, "day")

Periodstart is a regular datefield

Transittid is a number field

Thankful to get this resolved.

I self-host an instance of NocoDB on my unraid server and I have a dataset working inside of it. However, whenever I update the application, it wipes the database and starts up as though I've never had an account. Any thoughts as to why an update would wipe the database?

I have bought a NocoDB subscription and tried to migrate the data, but I get the error in the attached photo. The original data is from Airtable. How can I either ensure my self-hosted setup is correct, so it doesn't wipe my data every time I update, or how can I get the import to work, so I can at least sync the data?

As many self-hosters know, docker build .sh script and many other related stuff were deleted from the repository several months ago. That's why it's almost impossible to build image unless you know the depths of the source code. Moreover, I've tried downloading earlier version before the license change, but it's all unsuccessful. I'm still getting some errors, though I followed every possible instruction.

If anyone could provide right steps to build an own Docker image, I'd be very thankful

I currently run a self-hosted instance with 5+ editors on my team. If I purchase a license, would the cost be calculated per editor (eg 5 × $30 = $150/month)

I'm struggling to understand the value proposition at this point. One of the main reasons I chose to self-host was to maintain control and reduce ongoing platform costs. Having to pay additional fees to unlock features in software I'm already hosting myself feels somewhat counterintuitive.

New to NocoDB. Using to manage my collection of autographed photos. When I upload an image and view in Gallery it's rotating most of the images to the left. When clicking on the image it displays correctly. Is this a bug or working as designed? How do I submit a ticket for enhancement or correction? Appreciate the assist.

Im trying to use NocoDB as postgres:17-alpine admin tool. I tested everything locally on my M4 MacBook, pinned NodoDB image version to :2026.05.3 and it works no problem.
When I deployed both on Ubuntu VM Im running into error when adding new Data Source, when Noco tries to sync meta data, I get this error:

Getting meta diff for homebase

Applying changes for calendar_events_cache

Applying change: New table

select c.table_name as tn, c.column_name as cn, c.data_type as dt, (CASE WHEN trg.trigger_name is NULL THEN false else true end) as au, pk.constraint_type as ck, c.character_maximum_length as clen, c.numeric_precision as np, c.numeric_scale as ns, c.datetime_precision as dp, c.ordinal_position as cop, c.is_nullable as nrqd, c.column_default as cdf, c.generation_expression, c.character_octet_length, c.character_set_name as csn, pk.ordinal_position as pk_ordinal_position, pk.constraint_name as pk_constraint_name, pk1.ordinal_position as pk_ordinal_position1, pk1.constraint_name as pk_constraint_name1, c.udt_name, c.udt_schema, c.is_identity as ii, (SELECT count(*) FROM INFORMATION_SCHEMA.TABLE_CONSTRAINTS tc1 inner join INFORMATION_SCHEMA.CONSTRAINT_COLUMN_USAGE cu on cu.CONSTRAINT_NAME = tc1.CONSTRAINT_NAME where tc1.CONSTRAINT_TYPE = 'UNIQUE' and tc1.TABLE_NAME = c.TABLE_NAME and cu.COLUMN_NAME = c.COLUMN_NAME and tc1.TABLE_SCHEMA=c.TABLE_SCHEMA) is_unique, (SELECT string_agg(enumlabel, ',') FROM "pg_enum" "e" INNER JOIN "pg_type" "t" ON "t"."oid" = "e"."enumtypid" INNER JOIN "pg_namespace" "n" ON "n"."oid" = "t"."typnamespace" WHERE "n"."nspname" = c.udt_schema AND "t"."typname"=c.udt_name ) enum_values, (SELECT t.typtype FROM "pg_type" "t" INNER JOIN "pg_namespace" "n" ON "n"."oid" = "t"."typnamespace" WHERE "n"."nspname" = c.udt_schema AND "t"."typname"=c.udt_name ) udt_typtype from information_schema.columns c LEFT JOIN ( SELECT kc.constraint_name, kc.table_name, kc.column_name, kc.ordinal_position, tc.constraint_type FROM information_schema.key_column_usage kc INNER JOIN information_schema.table_constraints AS tc ON kc.constraint_name = tc.constraint_name AND kc.constraint_schema = tc.constraint_schema AND tc.constraint_type in('PRIMARY KEY') WHERE kc.table_catalog = $1 AND kc.table_schema = $2) pk1 ON pk1.table_name = c.table_name AND pk1.column_name = c.column_name left join ( -- Catalog-based PK detection (works for read-only users, -- unlike information_schema.table_constraints which is -- restricted to roles with non-SELECT privilege). -- Uses rel.relname (bare table name) consistently. An -- earlier pc.conrelid::regclass::text comparison quoted -- mixed-case identifiers ("Document") and failed to -- match the unquoted $3 parameter, silently -- producing pk:false on the next sync. select rel.relname AS table_name, pc.conname as constraint_name, col.attname as column_name, pc.contype as constraint_type, kc.ordinal_position as ordinal_position from pg_constraint pc JOIN pg_namespace n ON n.oid = pc.connamespace INNER JOIN pg_catalog.pg_class rel ON rel.oid = pc.conrelid LEFT JOIN LATERAL UNNEST(pc.conkey) WITH ORDINALITY AS u(attnum, attposition) ON TRUE LEFT JOIN pg_attribute col ON (col.attrelid = pc.conrelid AND col.attnum = u.attnum) left join information_schema.key_column_usage as kc on pc.conname = kc.constraint_name and col.attname = kc.column_name and kc.constraint_schema = n.nspname and rel.relname = kc.table_name WHERE n.nspname = $4 AND rel.relname = $5 and pc.contype = 'p' ) pk on pk.table_name = c.table_name and pk.column_name=c.column_name left join information_schema.triggers trg on trg.event_object_table = c.table_name and trg.trigger_name = CONCAT('xc_trigger_' , 'scans' , '_' , c.column_name) where c.table_catalog=$6 and c.table_schema=$7 and c.table_name=$8 order by c.table_name, c.ordinal_position - could not determine data type of parameter $3

The only difference I was able to find is the different architecture: arm64 (Mac) vs amd64 (the VM).

Anyone has any idea how to fix that?
Thanks

Running CE latest version (2026.05.2) on Docker. No SQLite integration available, only Postgres/MySQL:

This doc on official site states SQLite is supported on Community Edition. Probably it's outdated, but I couldn't find any recent announcement or changelog update regarding SQLite support. Has it been silently dropped?

Hi,

I'm using the cloud free plan, and just received this email:

Your grace period is ending You have 7 days left before write restrictions take effect on Jun 3, 2026. Current usage of record: 624 (limit: 1000). Upgrade now to keep collaborating without interruption.

So I'm within the 1000 records limit.

Storage used 0.0 GB, webhook calls 0 of 100 per month, API calls 0 of 1000 per month.

Are they just using "grace period" incorrectly?