It looks like the function call worked either way, but that line change did it! Well... it threw other errors, but these ones were much more useful that the previous and I know how to fix them Thank you!

Tried embedding per your suggestion, the behavior did not change. 

No, that's the issue. That call just throws an error saying that it's "not a function". I don't understand why, I call a very similar function in a similar location and don't have this issue. 

Hi All, I am making a new fragment to help with some code a want to run often. I'm at the point where it should be working but whenever I attempt to reference it in the field I get an error saying "error: TypeError: form1.variables.employeeLookup.employeeLookupMain is not a function". I have no idea...

Just making the .mandatory= "disbaled" or "error" doesn't work. You have to first do the process I described originally where you make it visible, then modify the .mandatory property, then make it hidden again. You also can't call the fragment that does this from the validate event (where we were or...

Hi Mayank, I have way too many hidden required fields across my implementation of Webforms for it to be reasonable to go in and do that logic on each one of them. I need a way to solve this in a fragment script.  I've tried using that bitTextField1.mandatory = "error" but when I try and do that to ...

Hi all! This is related to a previous question that I've asked, but I think I narrowed things down quite a bit. I have a script (Fragment) that runs on submission that scans the form and makes all hidden-required fields optional, that way the form will submit as long as all of the visible required f...

Those console.log statements weren't in there until after this started, they are just there for debugging purposes. ValidationHTML is another fragment that is attached to the form. The second code block is the "setFocusToRequired" part of it. This method just handles turning text red and setting the...

Hello All!I have a script that is designed to scan through the form when the users submits it and make any hidden required fields un-required. However, recently after a change to the default profile (I think this was the inciting incident, I'm not entirely sure), the user has to press the submit but...

Hi All! We made the decision to switch off of PDF forms to HTML5 forms as part of an upgrade to our livecycle environment. In the old PDF forms, any fields that could be edited by a user had a nice highlight around them to make it clear that they weren't protected. In HTML5, this is off by default, ...