Tag Info

New answers tagged

0

Found the issue. I was not including a the clienttemplates.js... Eventhough it was appearing in Chrome resources. <script type="text/javascript" src="js/clienttemplates.js"></script>


0

Refer the below link which explains how to override the people picker to provide the valid values. http://blogs.msdn.com/b/kaevans/archive/2013/05/26/fixing-people-picker-for-saml-claims-users-using-ldap.aspx


0

I ended up rebuilding the list, at which point I had the option to look up the field using the 'Workflow Lookup for a User' and 'Current List' option. I'd made some changes to the original list, such as allowing management of content types (and some other changes I don't remember) which seem to have limited my options. Since falaskaman's above comment is ...


0

For anyone else wondering, here's the answer... Back in May I ran gpresult against user A and user B. I compared both users and noticed one difference. I'm still not sure why, but user A had a single registry key group policy preference that was not applied like the rest of the users in the entire domain. Thus, user B had all the same group membership, ...


1

When creating a workflow choose the "Assign a To-Do Item", then when choosing users, select "Workflow Look up for a user" and select "Current List", and the "Assigned to" or whatever the field name you want to draw the users from. I tried to reword my previous comment in to a more general answer. EDIT: changed my reply form the unhelpful one, to the ...


0

It is also possible this user has been deleted in Active Directory and re-created afterwards with the same username and group. The problem is that when a user is recreated with the same details (username, groups, ...), the SID is not the same! This means that for SharePoint the old user with username domainjax\JohnDoe is not the same as the re-created ...


0

KHA - try to fix this issue with browser compatibility, add main site to the list of compatible sites! actually this issue became after 9th IE!


0

I resolved this for a customer by running stsadm -o adduser on the SharePoint server. Through the Web interface the error remains but with stsadm it is possible to add the user to the appropriate group.


2

Use the following code: <script type="text/javascript"> function SetPickerValue(pickerid, key, dispval) { var xml = '<Entities Append="False" Error="" Separator=";" MaxHeight="3">'; xml = xml + PreparePickerEntityXml(key, dispval); xml = xml + '</Entities>'; EntityEditorCallback(xml, pickerid, true); } function ...


1

I did this exact thing this week. Use a REST call and populate the people picker. I used an excerpt from : http://lixuan0125.wordpress.com/2013/05/10/sharepoint-2013-get-current-user-loginname-using-jsom-rest/ $(document).ready(function () { var userid = _spPageContextInfo.userId; function GetUserLogin() { var requestUri = ...


2

same error and similar issue, its for 2010 but the solutions should still work! The error lie's within active directory user, as other users from the same or other domains work. saying this, there could be another problem... do you have a root site? System.Runtime.InteropServices.COMException: The user does not exist or is not unique. at ...



Top 50 recent answers are included