I have a list box on a sub-form used in a dialog window.
The values are listed with unique aliases, but the displayed values are duplicates, and the listbox field does NOT allow “multiple values”… so the values looks like this.
XX|0
XX|1
XX|2
XX|3
When the user selects a value, all aliases are returned as a multi-valued item despite the field settings stating otherwise. If I then change the displayed lookup values to be unique, but still with the same aliases, like this
XX|0
XY|1
XZ|2
ZZ|3
the a unique value is returned correctly. This seems to be a bug in 8.0.2. Can anyone else confirm ?
Not sure it’s a bug though, the field has a value XX, which has multiple aliases. What are you trying to achieve by this? It seems a strange thing to do
Subject: Yes it’s strange… but listbox functionality is stranger
The data is derived from another system. But if i have distinct alias values (ie 0,1,2,3 etc) and the field is NOT allowing multi-valued select, but then returns multi-values based on the displayed value, that’s a bug to me.
If you have distinct aliases, list box should be able to work it out.