!= In relevant field - Is this still not acceptable

LeonardBarnhill

This question was brought up in 2017, is the use of "not equal" still not acceptable in the Relevant field?  I have the statement selected(${StrucDetail} != 'JCT') that generates an error message when the XLSForm is saved:

"Error evaluating field 'StrucDiam': The problem is located in Relevant expression for S{StrucDiam}  ... cannot handle function 'selected' requires 2 arguments ...

There is a long list of Choices for the StrucDetail select_one STRUCTYP and this is the only one not needing a diameter .

Suggestions please

XLSForm screenshot.JPG

AlfredBaldenweck_4-1713547066707.png

dougbrowning

First you have the parens in the wrong spot. Should be  selected(${StrucDetail}) != 'JCT'.  But I think selected returns true.  So just selected(${StrucDetail}) may work.

You only really need to use selected for select multiple.  Did you try just ${StrucDetail} != 'JCT'?

Hope that helps