I can't find a clear answer on this... I need people picker control to see distribution lists. I added DL to the selectionset in ACLinv.aspx, it still doesn't show the dist. lists, even after a reboot. All I need is the people picker on a newform or editform to be able to choose a distribution list.
I don't want to (if i don't need to) create an AD security group and add the users to it because that adds to the users security foot print which just muddies things.
I'm using SP2007.
thanks for any help.
According to your description, how can you specify if the users can pick a user or a security group or a distribution list?
Well, the answer was in the SDK - there is a property "SelectionSet" that accepts a comma-delimited list of strings that say what can be picked.
For example, "User,DL,SecGroup" will allow users to pick user accounts, distribution lists and security groups. Choosing just "User" will allow only people accounts. The sharepoint people picker ususaly sets "User,SecGroup,SPGroup" or "User,SecGroup" or just "User”. For more information,please refer to:
Thanks for your reply but as I noted in my original question I've already added DL to the SelectionSet attribute of the PeopleEditor control on
the ACLinv.aspx page in the Template\layouts directory of the 12 hive. But there's been no functional difference using the control on any of the site pages.
SharePoint only uses Security Groups for permissions - I have never heard of making this work with DLs. Other Windows-based systems only use Security Groups as well. DLs should not be usedy for security - only for email groups when permissions will NEVER be needed, such as when the DL includes non-employees. Otherwise, all the DLs should just be SGs, because they get the same functionality PLUS the ability to be used for permissions.
Why do you have DLs instead of SGs, and why do you not want to create SGs for use in SharePoint? It's a best practice to do so. I didn't understand your concern about security footprint and "muddying" things. If you deploy SharePoint, part of the initial planning always includes security and AD groups - this gets planned WAY in advance of deploying SharePoint.
It's just a simple radio button change to switch a DL to an SG.
SharePoint Architect || Microsoft MVP || My Blog
Planet Technologies || SharePoint Task Force
Thanks for your reply. I'm not trying to use DL for permissions just a simple email where the user wants to be able to choose a distribution list instead of indivual people on their form. Maybe I'm not understanding something, when talking about security groups and DL we are both talking about AD correct?
My problem with SG is creating a security group just for the sole purpose of the people in the group getting an email via SharePoint doesn't seem to make sense.
At any rate, I guess I'll just switch the DL to a SG and be done with it.
You want to create a distribution group if you intend to use the group for email distribution rather than for security.
Adding a user to a large number of security groups will increase the size of the user's security token (e.g. NTFS, Public Folder permission), a problem that will be avoided by using distribution groups where a security context is not required.