Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pieople picker scope #63

Open
madrileanu opened this issue Jul 28, 2016 · 3 comments
Open

Pieople picker scope #63

madrileanu opened this issue Jul 28, 2016 · 3 comments

Comments

@madrileanu
Copy link

Hello,

I have managed to successfully setup the widget in my SharePoint hosted app, but i have noticed that the people picker is only retrieving users from local user information list and not from the entire directory. Is there a way to configure the widget in order to retrieve all the users?

Thank you,
Andrei.

@purtuga
Copy link
Owner

purtuga commented Jul 28, 2016

Hi Andrei.  The widget uses the SearchPrincipals operation of the People service API.  I don't see an option there to change how the search is done.  
https://msdn.microsoft.com/en-us/library/people.people.searchprincipals(v=office.12).aspx

Paul
-- sent from mobile

@madrileanu
Copy link
Author

Thank you for the response Paul.
As for my understanding , the client side people picker from MS: https://msdn.microsoft.com/en-us/library/office/jj713593.aspx is actually fetching all the users from SharePoint Online and as i know is also using principals. Why the people picker from the widget doesn't have the same behavior?
Thanks again Paul. I appreciate your work!

@purtuga
Copy link
Owner

purtuga commented Jul 28, 2016

I'll take a look at it.  This widget here is still using the SOAP APIs which have been frozen and are not longer updated (deprecated).  
It's possible that the REST or CSOM may support the additional attributes I see in the link you posted, mainly:     SearchPrincipalSource    ResolvePrincipalSource
I don't see these in SOAP.  

(also, FYI: this entire library is currently undergoing a huge rewrite to make it more modern and adaptable to O365/SP2013/16.  I'll look to see if the REST API supports the new params then)
Paul
-- sent from mobile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants