Restrict requested field in link to table modal

Technical Help
,
1

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

Self-hosted

If you are self-hosting, what version of Baserow are you running?

version 1.33.3

If you are self-hosting, which installation method do you use to run Baserow?

Docker version 28.1.1

What are the exact steps to reproduce this issue?

The fields filtered in modal does not match the requested field.
It could be a significant gain of performance in big table. Could it be added to the next version ?
The image shows display field (none), and here is the related truncated response from the API showing one row.

{
  "count": 39,
  "next": "http://baserow.grainerie.netlib.re/api/database/rows/table/558/?page=2&size=10&view_id=2345",
  "previous": null,
  "results": [
    {
      "id": 12,
      "order": "12.00000000000000000000",
      "field_5238": "SALLE DIFFUSION",
      "field_5239": "",
      "field_5240": "",
      "field_5241": "",
      "field_70479": [
        { "id": 120841, "value": "Lundi", "color": "darker-cyan" },
        { "id": 120842, "value": "Mardi", "color": "orange" },
        { "id": 120843, "value": "Mercredi", "color": "dark-brown" },
        { "id": 120844, "value": "Jeudi", "color": "darker-blue" },
        { "id": 120845, "value": "Vendredi", "color": "darker-gray" }
      ],
      "field_70480": { "id": 120705, "value": "09:00", "color": "dark-purple" },
      "field_70481": { "id": 120821, "value": "19:00", "color": "dark-purple" },
      "field_123186": "10.0",
      "field_124364": {
        "id": 221115,
        "value": "POSSIBLE",
        "color": "darker-green"
      },
      "field_141126": "1",
      "field_141426": [
        { "id": 252970, "value": "ACCUEIL EN CREA", "color": "purple" }
      ],
      "field_141967": "**SALLE JEANETTE MAC DONALD (Salle de  diffusion) (plateau 14m/ 12m h 10m sous grill) - accroches et ancrages**",
      "field_143275": null,
      "field_143276": null,
      "field_143277": {
        "id": 253790,
        "value": "NON",
        "color": "darker-orange"
      },
      "field_233897": "16",
      "field_238092": [
        {
          "id": 13,
          "value": "2024 - SALLE DIFFUSION | 350€",
          "order": "13.00000000000000000000"
        },
        {
          "id": 32,
          "value": "2023 - SALLE DIFFUSION | 350€",
          "order": "32.00000000000000000000"
        },
        {
          "id": 51,
          "value": "2025 - SALLE DIFFUSION | 350€",
          "order": "51.00000000000000000000"
        }
      ],
      "field_238096": "350",
      "field_238097": "350",
      "field_238098": "350",
      "field_238124": "0.05",
      "field_238125": "0.05",
      "field_238126": "0.05"
    },
(truncated)

Attach screenshots, videos, or logs that demonstrate the issue.

Capture d’écran du 2025-06-07 09-59-19.png
Capture d’écran du 2025-06-07 09-59-19.png1910×617 106 KB

2

In the same topic, hidden and not required fields are always fetched in request.
It could improve performances to adjust api request with appropriate include parameter, and do not fetch all field on all views.

What do you think ? :upside_down_face:

3

That’s a great idea, and I agree that server responses can be much faster by omitting the hidden fields. The only downside is that the page will need to reload with the missing fields whenever you want to view a field that was previously hidden, but that seems reasonable given the performance gains in all other cases.

I’ll create a GitLab issue to track this request. There’s already a lot of work underway for the next release, so I doubt this can be included, but I’ll keep it in mind for the following one. Thanks for the feedback!

4

Issue created: Only include visible fields in views and link row modals (#3679) · Issues · Baserow / baserow · GitLab

5

I’ll follow the updates ! Thanks for all this work :slight_smile: