mason3t

Christie,

Thanks for the reply. I just tried it out, unfortunately what you instructed me to do is not possible. I can only apply one condition per field (the checkbox is disabled in other conditions). I used a show condition originally, but the behavior is the same using a hide condition. I did notice that the html field seems to follow the behavior of the calculation field. That is, a pure html field (no magic tags) will show/hide just fine. However, if you include magic tags, it will only show once the values of the magic tags change. In my case, when the calculation for shows up blank, the html field is hidden, then when I change the value of the field that affects the calculation, the calculated value appears and the html field appears.

Also, I don’t think this is expected behavior. As I said towards the end of my last post, it is not reproducible. I have not looked at it for a couple of weeks, but when I tried to reproduce the problem on a simpler form, I could not (basically I just extracted only the affected fields and conditions from the complicated form). I will look back at my simple form test and let you know, but I am fairly sure I reproduced the conditions exactly and it worked as I had originally expected it to. So unless the form engine is purposely delaying calculations when there are a lot of fields (possible I suppose, maybe to avoid lag?), this should not be happening.

Finally, I have found another problem. If fields are hidden, the values come up as blank in the email to the client (despite the fields having a default value). This I can see being expected behavior, but I need a workaround to this, so that clients do not see a blank value in the email.

Thanks,
Mason