2
Central Management of Select Field Values
Source: twentyhq/twenty#16180 · opened by @fendle
In some cases, the same field needs to be reused across two or more objects. Currently, this requires re-entering the values for each Single Select and Multiple Select field separately. It should be possible to define and maintain Single Select and Multiple Select fields centrally and then reuse them across multiple objects, so that the list of values only needs to be managed in one place. Additionally: It should be possible to manage (create, update, delete) the selectable values not only via the UI, but also via an API. Users should be able to activate or deactivate individual values. Example use case A customer bought a specific notebook 2 years ago. This notebook is no longer available on the market. When a user now creates a new record and wants to select a notebook for a customer, the old notebook (which has been deactivated) should no longer be selectable. The user should only be able to select active values, while existing records keep their historical (now inactive) valu…
No pledges yet. Be the first to back this.
Comments
Similar requests
Add conditional field formatting for numeric table and record fields
3 votes · 0 comments
Resizable field column on the full-page record view (labels and values are truncated)
1 vote · 0 comments
Data Model Object table: Fields count includes relations, which isn't immediately clear to users on the object detail page
0 votes · 0 comments
Add toggle to select/multi-select field to dis/allow custom value creation
1 vote · 0 comments
New feature - Workflow UPDATE_RECORD allow different update modes (replace / append / only-if-null)
1 vote · 0 comments
No comments yet.