Hot answers tagged

3

I know this is old but that "waiting for server" is normally the server processing your request, this is due to structural navigation being generated, content queries or searches webparts being generated, too many webparts and so on, this is called TTFB or Time To First Byte. So your "Waiting for server" is not the amount of time it takes to send back the ...


2

As per the comment, It was URL issue. Valid URL is Shared Documents/NewFolderName Sabita S added another fix: Remove backslash (/) from data relative URL .It should be 'ServerRelativeUrl': 'Documents/NewFoldername' .... data:JSON.stringify({'__metadata': { 'type': 'SP.Folder' }, 'ServerRelativeUrl': 'Documents/NewFoldername'})


1

Code in sandboxed solution has been depricated by Microsoft in SharePoint Online for some time now, see Deprication of custom code in sandboxed solutions. So that might be a possible reason for what you are experiencing. That they are now enforcing the no-code-policy. What you need to do in that case is to convert your sandboxed solution to an add-in, ...


1

SharePoint Office 365 Admin has full control of every object. There is no way you can remove that. One option is to log details of users who are viewing the list/library. You can add JSOM script to capture this information. Also you can put a redirect logic in the pages so if the user is not part of say HR SPGroup then redirect to an access denied page.


1

I was faced with the same issue in a workplace that did not understand exactly how Microsoft products work and the answer is no, the administrator has higher power for a reason. What we have compromised on is to have a third party application that monitors accesses and creates daily/weekly reports so that every intrusion by administrators is justified before ...


1

JSOM Start SharePoint Workflows with JavaScript Client Object Model function LoadScripts(){ SP.SOD.executeFunc("sp.js", "SP.ClientContext" , function(){ SP.SOD.registerSod('sp.workflowservices.js', SP.Utilities.Utility.getLayoutsPageUrl('sp.workflowservices.js')); SP.SOD.executeFunc('sp.workflowservices.js', "SP.WorkflowServices....


1

Refresh the token in Form Digest The two most common ways are to either use ye olde web services and call into the /_vti_bin/sites.asmx and use the GetUpdatedFormDigest method. To use this you have to create a SOAP message and then parse the response and retrieve the updated token. You can then either pass that new token for your subsequent requests, or ...


1

The error message indicates that your App doesn't have permissions to do the add. You need to request write permission at the Web scope in the App manifest. You also need to change the GET to a POST.


1

If anyone's wondering, solved by implementing CORS on the server instance, allowing the app web to access data. Not the greatest solution as only one domain can be whitelisted per server instance, but it works.


1

I just came across this issue. This appears to be a limitation whereby SP.Utilities.CommandBlock does not get loaded to a published page in view mode. It will work for site collection admins, but not for owners/members/visitors. For non-site coll admins, the workaround is to check out the page, and then perform the drag-and-drop upload.



Only top voted, non community-wiki answers of a minimum length are eligible