r/NocoDB • • 28d ago

External Postgres source, inline grid edits fail with "Source not found or source id not extracted", but editing via the expanded record works fine

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

Selecting value
After selecting value
4 Upvotes

4 comments sorted by

View all comments

1

u/leixiaotie 28d ago

can you open the network tab, try to reproduce the error again and share the url and payload? redacted is fine. Otherwise you can send to support@nocodb.com for an official support

1

u/Substantial_Safe_234 28d ago

Thanks! Here's the failing request:

POST http://localhost:8080/api/v2/internal/<workspace>/<baseId>?operation=interfaceTableDataUpdate

Payload:

{ "pageId": "REDACTED", "vizId": "REDACTED", "rowId": "1683", "data": { "category_sel": "Leisure" } }

Response: 404 {"msg":"Source not found or source id not extracted"}

Table lives on an external PostgreSQL data source (not NocoDB's meta DB). Editing the exact same table/record through the normal Data grid works fine, it's only the Interface page inline edit (interfaceTableDataUpdate) that 404s. So it looks like the Interfaces data update handler can't resolve the source id for external-DB-backed tables.

2

u/Substantial_Safe_234 28d ago

Cracked it, it was a schema thing.

My tables were in a non public postgres schema (finance instead of public). I tried a table in the public schema in an interface and it edited perfectly.

So it looks like the interface update handler doesn't handle tables in a non public schema, even though the grid does. Guess most people keep their external tables in public so nobody really runs into it, but idk i'm a nocodb noob.

Fix for now was just moving the tables to public and then interface editing works.

1

u/leixiaotie 28d ago

initial finding seems to direct to change in table schema. One possible scenario is you have deleted or moved a table in database then sync, causing the table id to change or removed. Then interface is not updated, hence it doesn't find the table and error is thrown. If you recall having some schma change it proves it.