It's exceptionally over complicated but here is the whole story and why I have no other solution than to use the alternative URL.

It all started when a button called AutoFill showed up on the form because we have 2 conditions for the lookup. The button is both confusing to the users because no other lookups require it and it causes a violation of the lookup procedure.

The user can click the AutoFill button to "Manually" fill the lookup output field, then change the data of the conditional fields without pressing the button again. This effectively allows them to associate any value from the database with any selection regardless of it being accurate. They can select an account worth a million dollars and get it approved at $1.

The following lines of code, to work around this problem, execute differently depending on which URL is used to access the form.

  function autofill() {  
    $(this).closest("tr").find('button.autofill').trigger('click');
  }
  
  $('.lookuptrigger input').on('change',autofill);
  $('.cf-table-add-row').click(function () {
    $('.lookuptrigger input').on('change',autofill);
    $('.cf-table-block tr:last').find('button.autofill').trigger('click');
  });

And this works great in a majority of environments. However we have a huge collection of PC's running all different versions of Windows and in both IE and Chrome this specific part of the code never executes.

$('.cf-table-add-row').click(function () {
    $('.lookuptrigger input').on('change',autofill);
    $('.cf-table-block tr:last').find('button.autofill').trigger('click');

While this line still works

  $('.lookuptrigger input').on('change',autofill);

Now the work around, is to simply use the secret URL /Forms/form/new/#

SAME FORM, SAME JAVASCRIPT, SAME BROWSER, SAME COMPUTER. Instantly the code runs as specified.

Something about the URL changes the result of my code. There is no logical explanation for this. I have looked at the form while accessing it with both URL's and used the developer console to verify that my javascript is not being modified before it hits the local browser. How can the same instruction set, executing on the same machine, produce different results based on an address bar field in the browser.

What version of Forms are you using?