Please confirm that the bug report does not already exist
Steps to reproduce
Create two tables. Use the "Link" field. Fetch data via api.
Desired Behavior
The nested field is just a count not an array of nested objects like described in the release notes here:
https://nocodb.com/docs/changelog/2025.06.0#api-v3-beta--fewer-calls-cleaner-design
Embedded Relation Field Data
v2: When you listed records, relation fields returned only a count of linked records.
v3: The same endpoint now returns the full list of paginated linked records inline, so you can fetch related details in a single call—no more chasing separate endpoints.
{
"records": [
{
"id": 1,
"fields": {
"Title": "post 1",
"CreatedAt": "2025-12-09 08:03:40+00:00",
"UpdatedAt": "2025-12-09 08:04:57+00:00",
"post_interactions": 1
}
}
],
"nestedNext": null
}
If this were fixed, my other issue would probably be resolved.
Project Details
NocoDB Cloud
Attachments
No response
Please confirm that the bug report does not already exist
Steps to reproduce
Create two tables. Use the "Link" field. Fetch data via api.
Desired Behavior
The nested field is just a count not an array of nested objects like described in the release notes here:
https://nocodb.com/docs/changelog/2025.06.0#api-v3-beta--fewer-calls-cleaner-design
Embedded Relation Field Data
v2: When you listed records, relation fields returned only a count of linked records.
v3: The same endpoint now returns the full list of paginated linked records inline, so you can fetch related details in a single call—no more chasing separate endpoints.
If this were fixed, my other issue would probably be resolved.
Project Details
NocoDB Cloud
Attachments
No response