I found a strange result when investigating why a field I expected to be hidden was showing. The formula has many “OR” elements, like this:
@Name([CN];From) != @Name([CN];@UserName) | OnlineMeeting=“1” | EventID!=“” | AppointmentType!=“3” | (Flag!=“1” & (!@IsNewDoc & !SaD=“0”)) | Repeats = “1” & !@Contains(LocalParams;“B”)
I expected that it would hide if any of the OR statements is True, and the last statement should read as a single test like Repeats = “1” & !@Contains(LocalParams;“B” because AND comes before OR.
But it turns out that it gives the AND in the last test lower precedence than OR, so in effect it’s testing each of the cases AND the last, something like this…
(@Name([CN];From) != @Name([CN];@UserName) | OnlineMeeting=“1” | iwEventID!=“” | AppointmentType!=“3” | (iwFlag!=“1” & (!@IsNewDoc & !iwSaD=“0”)) | Repeats = “1”) & !@Contains(iwLocalParams;“B”)
My reading of the Help entry on precedence says AND comes before OR
Quote:
The following table summarizes the order of operator precedence. The operands in the table are binary except where noted. Operators on the same line have the same precedence. In order of highest-to-lowest, the precedence of LotusScript operators is:
Not
And
Or
Xor
Do I misunderstand?