InputEnabled bug in version 7?

HCL Domino Domino Forum
1

Hello,

I have a dialog list type field on a form, which I would like to enable/disable for input depending on the value of another (text) field on the form, which is “Computed for display”.

Say the dialog list field is called “Input”, the other “EditAllowed”.

To achieve this I used an InputEnabled formula. on the Input field.

The value of EditAllowed is “YES”

The InputEnabled formula on the Input field is “EditAllowed = “YES””

After the form is loaded, everything is fine. However, when I press F9 (or refresh programmatically) the Input field suddenly seems to become read-only. I can’t type anything in, the list of choices is inaccessible and the arrow button is reduced to a line when I try to click it.

However, if I change the EditAllowed field from “Computed for display” to “Computed” everything is fine. The unwanted side effect is that the EditAllowed field is saved to the document, which I don’t want.

Anyone know if this is a bug?

The best workaround I found so far is to change the EditAllowed field to “Computed” and then remove the field from the document in the Postsave event using LotusScript. Disadvantage is that the document is saved twice.

Any help appreciated.

Thanks

Matt

2

Subject: InputEnabled bug in version 7?

Hi Matt,

Input Enabled formula works on “Native Notes Style” fields and dialog list is by default “notes style” field.

Moreover An input enabled formula should evaluate to @True or @False. like

@If(EditAllowed=“Yes”;@True;@False)

I have cross checked your case and its working on my side. Though dialog list is a “notes style” field.

Hope this helps.

Best Regards,

Munish Kaushik

3

Subject: RE: InputEnabled bug in version 7?

Thanks Munish,

Funny thing is that the InputEnabled formula works perfectly fine if the EditAllowed field is set to “Computed”, even though it is a Notes Style field.

It seems there is no logical reasoning behind it not working properly when the field is “Computed for display”, which leads me to believe it is a bug or an unsupported feature.

Thanks

Matt