It actually does work, but for some reason only on the second click. When I first clicked it just moved the page to the top, then I scrolled down to the post with the attachment, clicked it again, and the download started.

Thanks, Mattias, that helped a lot. I was confused because I didn't understand the names related to each other, so your example clarified that. I found that one other thing I had to do is set my variables as universal variables in Form Properties, because they would not carry over to where I was calling them from when I ran the script. So ended up having to use ".value" for the variables. I have a bunch of submit buttons on this form, so I needed a way to create a consistent set of headings acro...

The best method is to change the text to uppercase as it's being typed in:Add this to the "change" event:xfa.event.change = xfa.event.change.toUpperCase();

FulufheloMM, could you please explain exactly how that works?

Thanks, I checked the "Preserve scripting changes" setting and it was already set. I had only one field set to global binding, so I disabled that and it still had the same problem. I do have a lot of the same field names in both sections, such as Departure Date, Return Date, etc.. It would be too much work to rename them all to unique names. The solution I found was to put a script in the docReady event of the main selector button (Domestic/Foreign), to re-apply the setInstances count when re-op...

Sorry, I cried victory too soon..... The form seems to "forget" that the instance was set to zero, and after I save it and reopen it, the previously deleted instance shows up with all blank fields. I've got the form saving to version 9.1 and later. Any ideas?

Thanks, SI_MSD7, it works!

I figured it out! It just needs to be like this://replace @ with "@domain.com"if (xfa.event.change == "@") { xfa.event.change = "@domain.com";}So it will generate the suffix string only when you press "@", and it allows corrections without duplication, etc.

Hello,I can't send you the form because it's an internal government form. But please tell me what the issue is. I have since adopted a different method of handling this situation -- I simply make the fields in the new row required and the general form validation handles any empty field errors upon submitting. If you need to hide/show the table dynamically or make the fields required/not required dynamically, you have to add some scripting to make the fields in the new row mandatory. For some rea...