The Foreign ID column in HubDB currently supports selecting multiple rows from a table. However, there are frequent instances where only a single reference is required. Relying solely on training and field description notes to enforce a single selection is inadequate for ensuring consistent data. To address this, it is crucial to implement a single-select option for the Foreign ID column in HubDB.
I fully support the suggestion to implement a single-select option for HubDB’s Foreign ID column.
There are many cases where selecting only one reference is essential.
For example, in a custom event management system, each event should be linked to a single venue from a venue table. Similarly, in a job board setup, a job listing should be tied to only one department.
Relying on training or field descriptions to limit selections is not enough to ensure consistent data. A single-select option would make managing these scenarios much more efficient and reliable.