Minor bug spotted
Under review
September 01, 2025
Ref. See AlisQI Bot discussion 01-09-2025
I had mistakenly converted a selection list that was used in a set as a lookup list to numeric type, invalidating the function.
When I finally found out this problem, after a convoluted dead-end quest for inaccessable internal ID values led by Bot, some values in the list refused to work while most did, an error message read they were an 'inactive' option numbers value.
Maybe the values were buffered weirdly and stuck in numeric mode as the reference to number in the error message indicates.
Editing the stuck selection option values fixed the issue.