nextcloud / nextcloud/tables

Technical names/keys for select field option values

Open
#2,384 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
JavaScript
Stars
214
Forks
52
Avg merge
1d 10h
Merged PRs (30d)
82

Description

Is your feature request related to a problem? Please describe.

When reading table data from the Nextcloud tables API via N8N, I get numeric values for option fields back ("2").
The meaning of these values can change when new options are added to a field.

Describe the solution you'd like

When adding options to a select field, there should be a way to provide a technical key.
Example:

  • Create new column "Status" of type "selection" (single)
  • Add new option "Neu" with key "new"
  • Add new option "Gesendet an Geschäftsführung" with key "gf-sent"
  • Add new option "Freigabe durch Geschäftsführung" with key "cleared"

To use only a single field, one could split key + title with "|": new|Neu.

This technical keys shall then be returned when fetching row/column data, instead of the numeric option IDs.

Describe alternatives you've considered

No response

Screenshot
Image

When adding a new option value between 3 and 4 (by adding a new option, moving the 4 title to it, and changing the previous 4 value) , the internal value IDs change.

Additional context

Related: #1840 (for column names)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the Nextcloud Tables API paths for creating select-field options and fetching row or column data. Determine how technical keys should be stored and exposed, then verify that keys remain stable when options are inserted, reordered, or renamed and that API responses use them instead of numeric IDs.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.