Eric, the jQuery you supplied has been working great. We just added a Field Rule though to show a field if a value from another field is selected. What we are seeing is that the domain\\ value is being added multiple times now. Is there a way to get around this?

What we are seeing is similar to this for the value of the field: "domain\domain\domain\SMITCARR"

Bert, I like your thinking. This is what I've come up with so far, but it does not seem to be working correctly as it does not add the domain at the beginning. Any ideas what I have set incorrect?

$('.name').change(function() {
    if ($('.name input').val:contains('d91_domain\\')) {
     
    } else {
     $('.name input').val('d91_domain\\' + $('.name input').val())
    };
  });

There is a document ready function at the beginning with the correct closing tags.

So the ":contains" filter apparently doesn't work with input fields. Any other ideas of how to compare text?

You could try something like this to see if the domain is already there, or you could only call this code on the initial submission.

$(document).ready(function() {
  $('.name').change(function() {
    if ( $('.name input').val().indexOf('domain\\') == -1 ){
         $('.name input').val('domain\\' + $('.name input').val());      
    }   
  });
});

Eric, almost there. We have two fields that have been assigned the class name. With the latest code you posted, domain\ only gets applied to the first one. I would have thought that it would apply to all fields that match that class. Any idea on how to get it to apply to the second field as well?

I did some more troubleshooting and I think this is what's happening. The initial field with the name class is populated by a lookup that happens when the form first loads. The second field with the name class is populated from a lookup after a selection is made on the form. It does not appear to add the domain\ once the second field is populated.

I'm guessing I need to use the .each() function within the code you supplied?

You need to put this in a repeatable section, that iterates through the rows of the table, and then searches that row for the field in question to modify it.

$(document).ready(function() {
  function updateName() {
    $('cf-table-block tbody tr').each(function () {
    if ( $(this).find('.name input').val().indexOf('domain\\') == -1 ){
         $(this).find('.name input').val('domain\\' + $(this).find('.name input').val());      
    }   
    });

  });
$('.name').change(updateName);
});

It's not within a table though. They are just two single line fields.

$(document).ready(function() {
  function updateName() {
    $('.name input').each(function () {
    if ( $(this).val().indexOf('domain\\') == -1 ){
         $(this).val('domain\\' + $(this).val());      
    }   
    });

  });
$('.name').change(updateName);
});

Or:

$(document).ready(function() {
  $('.name input').change(function() {
    if ( $(this).val().indexOf('domain\\') == -1 ){
         $(this).val('domain\\' + $(this).val());      
    }   
  });
});

Both those should work then (have not tested either though)

The first one did not work, but the second one did. Thank you for your help guys!

I have fixed the first one, I left in the find thing like it was in a table, but have now removed it to allow it to function if you wanted to use it

We just upgraded to 9.2 and the following code you supplied stopped getting applied to the beginning of the field value. Any ideas why it doesn't work anymore?

$('.name').change(function () {
        $('.name input').val('domain\\' + $('.name input').val());
    });

It should still be working. Have you modified the code at all? There could be an error.

Eric, no, what I posted is what we have, with the exception of the real domain. The username populates from the token, but the domain is never prepended. This affects almost every form we have.

I have tested it and it happens in both IE 11 and the latest version of Chrome.

When I look at the code with Developer Tools in IE11 and I browse to the field in question, I do not see that it has the css class that I have assigned to it of 'name'. Is that the problem? The 'name' class is being applied to the <li> tag before the field.

The issue appears to be that the jquery change event isn't being run when the form is initially loaded and the field is automatically populated via lookup. We can see that this is something that worked in Forms 9.1 and no longer works in Forms 9.2. A bug has been filed and we'll update this thread when more information is available.

Hey there, a quick fix for this problem will be changing the line

$(document).ready(function() {
  $('.name').change(function() {
    $('.name input').val('domain\\' + $('.name input').val());
  });
});

to

$(document).ready(function() {
  $('.name').on('change lookup', function() {
    $('.name input').val('domain\\' + $('.name input').val());
  });
});

This should bring back old behavior. Let me know if this at least restores previous functionality for now while we look into it.

How do we alter this new code to apply to two different fields with the .name class? For example, we have two fields with the name class. The first field is changed when right after the form loads by doing a lookup. The second field is changed after some additional information is entered into the form and then a second lookup is performed. The first field is populating correctly, but the second one does not apply the domain\ once the second lookup is performed.

The code should work in both cases. There may be a small class difference, so what you can do is the following:

$(document).ready(function() {
  $('.name, .name input').on('change lookup', function() {
    $(this).val('domain\\' + $(this).val());
  });
});

I've added the ".name input" selector to also target the field, which may be because the name class isn't included in the input field (depending on your browser, the <input> element is what should ideally be targeted by this rule. If the <input> element does not have the class ".name", it's possible that only the ".name input" is necessary). I've also changed the inner function to target the changing field. Let me know if this works.

Edited out bolding since it didn't seem to work properly.

That breaks both fields.