_req using ktlCond

[kpmcdona63]

I am trying to require a field in a form view based on the value of another field and am getting a weird result - the field on which the condition is based is being required along with the field that I want to require. The condition is not respected.

Here is sample code entered in the Respond view's description:

_req=Notes, [ktlCond, has, test, NotesOld, Respond]

The expected result is that if "test" is entered in the NotesOld field in the Respond view then the Notes field (also in the Respond view) will be required.

Instead, both Notes and NotesOld are required regardless of what I type into the NotesOld field.

Yes, formPreValidation is set to true. Notes is a paragraph text field and NotesOld is a short text field.

Any idea what I am doing wrong?

[CSWinnall]

I don't believe it will work on a form input.
I have already raised this as an issue.

Can you try adding square brackets around your first parameter.

_req=[Notes] , [ktlCond, has, test, NotesOld, Respond]

When using parameter groups the square brackets matter.

Craig

[kpmcdona63]

Hey Craig,

Adding square brackets around the Notes field as you suggested causes it to not require either field. This is true even if I put "test" in the NotesOld field. It appeared to just break the keyword, but...

I changed the "against value" field to a field on a details view on the same page and it works with the brackets.

_req=[Notes], [ktlCond, has, TEST, Description, view_708]

From this I infer that the brackets are needed as you suggest and that the condition "against value" field has to be in a details view, not a form view. (I had previously tried using a read only field on the form view but it didn't work.)

This is supported by the documentation that says "The ktlCond option supports Details views." I guess a form view just doesn't work, which is a shame since I really would love to be able to force my users to fill out a field based on their response in another field.

The specific example here is "When responding to a request, if the user sets the Response field to "Object" then require the "Notes" field." so that there is context for why the user objected to the request. I might be able to implement this without _req by having two separate form views - one for object and one for confirm--but it is less elegant.

Is there a way for me to +1 your issue?

Thanks for your assistance!