cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
ScottVA
Level 3

Conditional Check Character Length Limitation in Dialog Control Behavior

One thing that we have run across during our installer development is a conditional check character limitation when defining an action for a Next PushButton control.

When defining a "Disable" or "Enable" action for the "Next" button on our dialog when a certain condition is met, this works

((EXADMPWD1 = EXADMPWD2) AND (EXADMPWD1 = "")) OR ((EXUSRPWD1 = EXUSRPWD2) AND (EXUSRPWD1 = ""))

but this does not

((REALLYLONGEXAMPLEADMINPASSWORD1 = REALLYLONGEXAMPLEADMINPASSWORD2) AND (REALLYLONGEXAMPLEADMINPASSWORD1 = "")) OR ((REALLYLONGEXAMPLEUSERPASSWORD1 = REALLYLONGEXAMPLEUSERPASSWORD2) AND (REALLYLONGEXAMPLEUSERPASSWORD1 = ""))

We couldn't find any documentation to indicate a character length limitation for condition checks and it only seems to apply to dialog control condition checks; at least that we've seen so far. Is there any documentation or general knowledge about what our character lenght limitation is or is it we have to find out by trial and error?
Labels (1)
0 Kudos
1 Reply
MichaelU
Level 12 Flexeran
Level 12 Flexeran

The Condition column of the ControlCondition table has a 255 character limit specified. This is most likely the source of any limit you are encountering. For this particular case, perhaps you could split up your cases so you have two enable conditions and two corresponding disable conditions, such that exactly one of the four will trigger for any given set of property values.
0 Kudos