Using IN_SET operator with setCharacterCasing throws exception

[jventurini]

SmartClient Version: SNAPSHOT_v9.1d_2014-01-24/Enterprise Deployment (built 2014-01-24)
FF 25.0.1

I am using a FilterBuilder that has a DataSource with a TextItem field which uses the
'setCharacterCasing( CharacterCasing.UPPER )' to upper case data entry. When selecting the
operator 'is one of' (OperatorId.IN_SET) and then entering a comma delimited list of
values I am getting the error 'toUpperCase is not a function'.

This only occurs when I call 'upperTextItem.setCharacterCasing( CharacterCasing.UPPER )'
for the TextItem associated with the DataSourceField. When this line (see MyDataSource.java)
is commented out the exception does not occur. Also this error does not occur when using other
operators ('equals', 'starts with', etc.).

Here is the stack trace:
10:47:35.901:IBLR3:WARN:Log:TypeError: _1.toUpperCase is not a function
Stack from error.stack:
TextItem.setValue() @ builtinds/sc/modules/ISC_Forms.js:1365
DynamicForm.setItemValues() @ builtinds/sc/modules/ISC_Forms.js:339
DynamicForm.validate() @ builtinds/sc/modules/ISC_Forms.js:440
[a]MathFunction.invokeSuper() @ builtinds/sc/modules/ISC_Core.js:264
SearchForm.validate() @ builtinds/sc/modules/ISC_Forms.js:2070
FilterClause.buildValueItemList/<.blur() @ builtinds/sc/modules/ISC_DataBinding.js:2862
FormItem.elementBlur() @ builtinds/sc/modules/ISC_Forms.js:1026
DynamicForm.bubbleItemHandler() @ builtinds/sc/modules/ISC_Forms.js:487
DynamicForm.elementBlur() @ builtinds/sc/modules/ISC_Forms.js:500
FormItem._nativeElementBlur() @ builtinds/sc/modules/ISC_Forms.js:1012
[a]MathFunction.invokeSuper() @ builtinds/sc/modules/ISC_Core.js:264
[a]MathFunction.Super() @ builtinds/sc/modules/ISC_Core.js:256
TextItem._nativeElementBlur() @ builtinds/sc/modules/ISC_Forms.js:1348
FormItem.._nativeBlurHandler() @ builtinds/sc/modules/ISC_Forms.js:587
FormItem._nativeBlurHandler() @ builtinds/sc/modules/ISC_Forms.js:586
unnamed() @

Any ideas?

[Isomorphic]

A fix has been applied, you'll find this problem solved in the next nightly build (April 23 or later).