I'm aware, however I can't seem to set a people picker field with the create action, and I'm about of ideas to try. I just wondered if it would work better with update....because I'm about out of logical ideas.
Got it, just wanted to make sure. So have you tried setting your people picker list value to a text variable (not a people picker variable)... Also when you did this, did you try to log the value of the text variable in the workflow to see what kind of output it is giving you? I've had to work through similar errors in the past so I know how frustrating it can get.
Sorry, I was sharp this morning. To answer your question, yes, I've had it log the text value to the workflow history, and it shows up correctly as the user's name, however I still get the error about the field being read only. What should I try next?
Am I understanding your requirements correctly? You have List A with Fields one of them is a people picker. You want to create a new Item in List B with some fields and the Name from the people picker in List A.
Have you tried to create the New Item in List B with out the people picker? Just to make sure that the action works. and to confirm that the action is set up correctly.
Hi Melissa Castillo,
Yes, that is correct. The action works without setting the people picker field, and it also works if instead of a people picker in list B, it's a single line of text. I can get the variable of the person's name to print to the log history and it prints the correct thing.
It seems like it should work, so I'm not sure why it doesn't.
I was binding he values in the form with js and had similar issue. I did following things:
No problem. The reason I asked if you printed the people name stored in the text variable to see if there was issues with the formatting. Sometimes to get this to work I had to mod the string result to make it something like domain\username to get it to work correctly, removing all other characters. Each env. seems to treat this a bit differently.
For testing you may want to hardcode a user name on the first attempt with domain\username to see if the update goes through correctly. Then you could swap out the hardcoded value for the people picker value and parse the string into the correct format.
This maybe a reiteration and i apologize if it is, but if you create a new variable then set that Variable to get User Profile "Name" and equal that Value to domain\username. This will have the users Full Name stored in varGetName then use the Update Item to past the variable "varGetName" to List B. Perhaps, it maybe best to export your workflow and share it here to get a better understanding on what it is that you are trying to achieve?
Here's a link to a posting that details how to set multiple people. For future reference: how to update Person/Group Field with multiple values using Nintex Workflow 2013