Convert Local Variable to Array

Question

Hello, 
 I am using local variable as a filter for a query: 
 
 a!queryFilter( field: "codigoMunicipio", operator: "IN", value: local!municipioMultiple ) 
 Problem is tha the variable is passed as String and the filter have condition IN 
 Which generates the following error: 
 
 Could not display interface. Please check definition and inputs. Interface Definition: Expression evaluation error in rule 'tax_colopoc' at function a!gridField [line 310]: Cannot apply operator [IN] to field [importMonth] when comparing to value [TypedValue[it=3,v=January]]. 
 Any idea how to pass it as an array {"January"} ?

ankita0004 · Accepted Answer

Looking like it is a type casting issue, try like this for once 
 a!queryFilter( field: "codigoMunicipio", operator: "IN", value: { 
 touniformstring( 
 local!municipioMultiple 
 ) } )

Siddharth · Answer

Hi Vladmir - Pass your value argument in {} braces. That should hopefully solve your issue. 
 a!queryFilter(
field: "codigoMunicipio",
operator: "IN",
value: {local!municipioMultiple}
)

Mike Schmitt · Answer

Are you seeing the error immediately upon trying to load the interface? If so, then my first guess is that since you're initializing local!municipioMultiple with no value, this is resulting in it having a non-multiple "null" value, which the query wouldn't like. So the first and easiest thing I'd suggest you change is in your variable definition, set the initial value like: 
 local!municipioMultiple: {}, 
 Also, you will probably need to do this conversion for local!searchMonth also, since that seems to be the one your error message is actually complaining about. And any other local variables that are passed into the query with the assumption that they're an array (though from a quick scan of your code, it appears those might be the only two). 
 As a side note: a good practice in general is to create an Expression Rule to handle any Query Entity which might be used in more than one place in the system. They can be set up to be flexible and easily handle multiple different use cases with multiple different assumed input sets, with little to no extra effort. I bring this up mainly because if you had done this for yours already, you likely wouldn't be having the error you're getting, due to the fact that you would have had to type cast these two filter variables as "array" type in the Rule Inputs of the expression rule, and therefore they'd manually typecast even a blank non-array incoming string as an empty set, and not break the query when doing the initial page load with no filter data set.

Convert Local Variable to Array

Top Replies