Cannot destructure property ‘type’ of ‘t’ as it is undefined

External Data Source
1

Hi guys,

I get an error when I try to change the name/description/other properties of a “Link to another record” column. The error is as follows:
Cannot destructure property ‘type’ of ‘t’ as it is undefined.

When googling this error message, it seems like its a JavaScript error message. Is this an error on NocoDB’s side or something in my setup (using AlloyDB for Postgres in GCP as the external datasource/db).

Thank you!

2

We have an internal issue created for this. And the fix should be there EOD or Monday.

Are you using cloud / self hosted ?

3

Than you. Self hosted

4

I’m still getting this error. (Self-Hosted, just installed today)
”Cannot destructure property ‘type’ of ‘t’ as it is undefined.”

Did a fix for this come out already?

Problem Example:
I have Posts and Users.
Posts with Editor and Creator. So in the posts sheet it has two link columns: “users” and “users”, and I’d like to change the name of the columns.

’users’ belongs to ‘users’
Foreign Key Column: user_id

5

Same on my end, I cannot rename “blue” relation fields (Has Many / reverse links) — Cannot destructure property 'type' of 't' error.

Environment
• NocoDB v0.265.1
• Self-hosted on AWS EC2 (Docker)
• External PostgreSQL database as data source

Problem
When trying to rename the blue relation fields (the reverse/“Has Many” relation icons) NocoDB shows this error:

Cannot destructure property 'type' of 't' as it is undefined

This happens both:

  • in the UI (Grid or Form view → column settings → rename), and

  • when using the Meta API:

    PATCH /api/v2/meta/columns/{columnId}
{ "title": "New Name" }

Regular columns and other relation types (one-to-one / belongs-to) update fine.
Only the blue “Has Many” relations trigger this internal error.

What I tried

  • “Sync with DB” (resync metadata)

  • Re-creating relations with “Link existing column”

  • PATCH via both /meta/columns/{id} and /meta/tables/{id}/columns/{id} endpoints

  • Verified the same behavior via API and UI

  • Not yet modified metadata directly in SQL (avoiding that for now)

Expected
Ability to rename or patch the display title of reverse/“Has Many” relations without error.

Example

One of my relation fields shows the table name instead of the column name, and I can’t change its title.

Notes / Screenshots

@Navi Is there a known workaround or temporary fix for this behavior?

6

Thanks for brining this to our notice. Issue is happening only with external DB tables. Created an issue here to track it further.