255 characters limitation in "Condition builder" textbox.

[fmoraleshtw]

Hi, 

We notice that in the Behavior  -> "Condition builder" it is not possible to introduce or edit conditions larger than 255 char, but if we edit the ".ism" manually and we fill the condition by hand, it works fine, it is displayed and the conditions is applied by Install Shield.

We use Install Shield 2019R3 (Version 25)

There is any way to fix this wrong behavior? . Split the clauses, that could be possible, could helps, but sometimes is difficult to understand the code and it would be desirable not apply this method in some cases.

Since the condition in background is being applied I assume that it is an error in the textbox definition or validation. 

Thanks

[Revenera_Ian · Accepted solution]

Hi @fmoraleshtw,

Thank you for your post.

What you are describing is InstallShield and Microsoft's Windows Installer behavior by design. There is a 255 character limit on a condition. I checked and confirmed this in the Direct Editor > ControlCondition MSI table > Condition column (S255, for a string of 255 characters maximum) with InstallShield 2022 R1, which is the latest InstallShield version.

Albeit it's a previous post, but Michael, a previous InstallShield Software Engineer and previous InstallShield Engineering Manager, is absolutely correct about this and the information still applies, see the following link and attached screenshot:

https://community.flexera.com/t5/InstallShield-Forum/Conditional-Check-Character-Length-Limitation-in-Dialog-Control/m-p/64509/highlight/true

To clarify, we do not support directly modifying the project .ism file. This could have unintended consequences.

Please let us know if you have any questions or concerns. Thanks!

[fmoraleshtw]

Hi thanks, yes, we will try to split the condition, anyway, maybe it would be interesting to thinking in increase this register to at least 512 in futures releases, due to, although 255 could seem enough, in some use cases can not be enough and it is difficult to the user to find a work around. This increases the complexity of the solution.

[Revenera_Ian]

Hi @fmoraleshtw,

Thank you for your reply.

We'll need a support ticket (case) to track this issue. A case will allow us to submit an Enhancement request, if necessary, for tracking purposes. Could you please open a case with our Support Team, about this issue, by email at support@revenera.com or by phone at (877) 279-2853?

Please let us know if you have any questions or concerns. Thanks!