I’m grateful that the Table Editor can now use the domain of a column for dropdowns without the domain values needing to be in the table itself.
However, what would make it even better would be the ability to define the domain values from outside of the table itself. The reason is that a column’s domain must include all nominal values that are present; there is no way to exclude a nominal value from the domain if that value is in the column. This means that if some invalid value does find its way into the table, it becomes available in the drop-down, allowing users to enter the invalid value again and again.
How does an invalid value get into a column that is controlled by a dropdown? Via the copy-paste bug, whereby you can get paste any value you like by using Ctrl-V. I flagged this issue just over a year ago, but as far as I know, it has not been addressed (unless it has been fixed in a newer release than 4.7.2, which I am still using).
There might be other scenarios where invalid data gets into a table via other means, but this particular bug in combination with the column domain rules has led to real-world problems in one of our data apps.
The ultimate solution (in addition to fixing the copy-paste bug) would be to allow an optional input port to the Table Editor where you can list allowed values for each column in the table. That way, the dropdowns could work independently of the actual data in the table.
Anyway, that’s my feature request! And any news on the copy-paste bug would be appreciated.