New answers tagged

0

sp.site.exists(url) is great - thank you for noticing it. However there is currently bug in it: if current page's url (where pnp js code is executed) contains hashes then sp.site.exists(url) call results in 403 response. Looks like it parses parent url incorrectly in this case. As workaround you still need to use /_api/SP.Site.Exists API call for that (sp....


0

You can get the RoleAssignments of list items using single REST endpoint in below format: <siteUrl>/_api/Web/Lists/getByTitle('List Name')/items?$select=Title,RoleAssignments&$expand=RoleAssignments This will give you user PrincipalId which you can match with current user ID in client side code (JavaScript). <d:PrincipalId m:type="Edm....


0

It took a while, but in the end it turns out it can be done. Here I'm using Simple OData Client and a Service Reference to https://<host>/_vti_bin/TaxonomyClientService.asmx called WsSpTaxonomyService: public Guid? GetTermGuid(string siteUrl, string userName, string password, string domain, string listName, string fieldInternalName, string termLabel) ...


Top 50 recent answers are included