AnsweredAssumed Answered

The user does not exist or is not unique.

Question asked by jeff on Mar 23, 2017
Latest reply on Jul 11, 2017 by bamaeric

SharePoint 2013, "Call web service" action to "UpdateListItems" I'm passing this to update a list item in another web:

 

<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:m="http://schemas.microsoft.com/sharepoint/soap/">

<soap:Header>

</soap:Header>

<soap:Body>

   <m:UpdateListItems>

   <m:listName>OIG IT Support Ticket Tracking</m:listName>

     <m:updates>

     <Batch PreCalc='TRUE' OnError='Continue'>

       <Method ID='1' Cmd='Update'>

         <Field Name='ID'>1234</Field>

         <Field Name='Data_x0020_Services_x0020_Ticket'>Completed</Field>

       </Method>

     </Batch>

     </m:updates>

   </m:UpdateListItems>

</soap:Body>

</soap:Envelope>

 

It works great almost all the time; however, for some records it returns this error:

 

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <soap:Body>
    <UpdateListItemsResponse xmlns="http://schemas.microsoft.com/sharepoint/soap/">
      <UpdateListItemsResult>
        <Results>
          <Result ID="1,Update">
            <ErrorCode>0x81020054</ErrorCode>
            <ErrorText>The user does not exist or is not unique.</ErrorText>
            <z:row ows_...loads of awesome data... />
          </Result>
        </Results>
      </UpdateListItemsResult>
    </UpdateListItemsResponse>
  </soap:Body>
</soap:Envelope>

 

As far as I can tell, any user in a Created By, Modified By, or "People Picker" type field in the target record is a current, valid user, and often the same users that appear in other non-problem records.

 

Intuition says this is probably some SharePoint problem and nothing to do with Nintex, but maybe someone else has run into this?

 

I suppose I should add that we just (over the weekend) upgraded from 2010 to 2013; however, I'm finding indications that this has been happening for several months.

 

Any help would be appreciated.

Outcomes