Hi @Dataland , this might be a long-shot, but I vaguely recall encountering something similar when mapping the options of an editable column.
I think it came down to case sensitivity between the underlying values and the mapped options (used for potentially selecting a new value in the cell and saving it back to the source).
Can you double-check the casing of the values and the options to rule that out?
Hi @dguzzo, thanks for the tip. The tables and field names were correct; but I did find that the data type of the 2 fields I was mapping together were different. One was an integer and the other was a varchar holding integers. Change the varchar to be an integer and everything started working.
Good to know that the data type of the mapped fields need to match!
Thanks again.