Tag Info

New answers tagged

0

It might be getting overridden somewhere else. You can try #resultcontent { height:350px !important; } Also, the x64 version of IE typically does not play well with SharePoint. Try the 32 bit version.


1

I have used the following javascript to set people pickers on new/edit forms in SP2013: First you need to get the loginName for the user, you could extract the ID from the value you got and use it to get the loginName through a REST query: var requestUri = _spPageContextInfo.webAbsoluteUrl + "/_api/web/getuserbyid(" + userid + ")"; $.ajax({ url : ...


1

Take a look at this link http://sympmarc.com/2012/04/22/working-with-sharepoint-people-pickers-with-jquery-a-new-function-called-findpeoplepicker/ And use following code to set picker value siteContactPeoplePicker = $().findPeoplePicker({ peoplePickerDisplayName: "Site Contact", valueToSet: $().SPServices.SPGetCurrentUser() });


1

You can add multiple forests and or domains by listing multiple domains or forests in the format Forest/Domain:DnsName,LoginName,Password separated by semicolons. For e.g. STSADM.exe -o setproperty-propertyname peoplepicker-searchadforests -propertyvalue“forest:Contoso.com,Contoso\User1,PasswordofUser1; ...


0

Like @Matt, I discovered that this was a permissions issue. I have a SharePointServerFarm account that runs the application pools and other various SharePoint services. I mapped this user to my forms database, and gave it the db_owner role. This fixed the issue.


0

By default, the GC service is used (port 3268-3269) to query the DCs. When working with external forest/domains, things start to get a little different. I suggest reading the following 2 articles about the subject: ...



Top 50 recent answers are included