Hello,
Hopefully there is someone else out there working with a dynamic window with this many fields. There are 13 fields on this window altered by this same calculation.
I think there is a problem with the process that checks for blank mandatory fields, in that it does not always have the latest mandatory true/false values reflected in the window when saving and checking for blank mandatory fields. Especially fields that were hidden when updated again to mandatory false.
If I change the calculated field more than once, sometimes the set mandatory false does not work. Clearing the calculate on change dropdown, then reselecting a value does workaround the issue, but here is a screen shot of my calculation displaying the correct thing, but the window will not let me save thinking those fields are still mandatory. My users will have a problem if they select the wrong issue and need to change it. I may be forced to set the calculate on change dropdown to read only after selection, making it a 1 time only selection. But this would force users to cancel the ticket and some will become confused.
In my example below, _PBInvNum and _PBInvDate were mandatory true at one time, but were changed to mandatory false when a 2nd issue type was selected afterwards. This seems to be only related to fields that were also hidden when changed to mandatory false. Almost as if the window check only updates the mandatory status of visible fields, possible unaware that certain now hidden fields are no longer mandatory.
PS - all the true/false values in my actual calculation are lowercase.
Thanks!
Mike
