Hi Sheila,

Double check if the field on the second form is set to read only?

Another way to do this is on that second form, create a new field, and again use the default value of {/_currentuser}.

What's happening is the field is getting set on the first form, and then since you're using the same field on the second form, it's passing that data through instead of updating it.

Now you'll have two fields, the current user who did Form1, and the current user who did Form2.

Cheers,

Carl

Hi, Carl. Thanks for responding.

The problem is that we're only using one form for several steps in the process and those steps can loop, depending on field entries. One of those steps sends the form to the current user, which won't necessarily be the same on repeat loops. That means even if I were to create another form, which I don't want to do because it increases the maintenance cost of the forms process, that solution would only work if the process went smoothly all the way through (no loop backs).

There's no way I can determine how many people will handle the form in a given instance, so I need to rely on one field that gets reset as it gets passed from user to user.

I can't believe I'm the only person who has a process like this, and am wondering how others worked around it.

Ahhhh.... I found the way to do it. Rather than using a variable in the default setting, I'm using a lookup rule to populate the field.  When _(Current User) matches a column in our database, use that value in the field.

Thanks!