0

I'm running SharePoint Foundation 2013.

I have a list that I'm trying to migrate from one site collection to another. I have used Export-SPWeb and also saving the list as a template (with content) via the GUI, but the list comes up on the new site collection with the people picker name matching another user's name.

I'm guessing this has to do with the AD users being imported to the new site collection at different times and they have different IDs, but that's just a guess.

Is there a good way to resolve this issue? I still need a people picker, but not matched to the wrong name. Thanks.

Improve this question
1
  • Not really, the List will use the internal ID of the source object (person) and that ID will not match the destination object (person) with the User Info List. Export-SPWeb is not high-fidelity, unfortunately. You will see lookup references break in various ways.
    – user6024
    Mar 24, 2016 at 19:38

1 Answer 1

Reset to default
0

People picker will resolve to the site collection's User Info Table first. Try adding the missing user to the site.? Also, I have the issue that we have users in 5 domains. SharePoint is in one. It will resolve to an account in its home domain by default. I have to specify an alternate domain to find a specific user or utilize the search/browse function of people picker.

You could make a SP group that has the users you want and ensure the field only looks up from that group instead of from AD.

Improve this answer
1
  • The same users appear in both sites, just with different db ID's, so I don't think that will work. Unfortunately the list is already populated, so creating a SP group resolve the issue.
    – Dude
    Mar 24, 2016 at 20:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.