New answers tagged library
This scenario occurs if you have a one-way trust established and are performing a search with a user from the trusted domain. One Way Trust DiagramIn order to rectify this situation, you’ll have to configure your Search Service Application to store ACLs in Claims format. To do this, you’ll have to use PowerShell (credit goes to Sladecross for this). ...
Please check this blog https://support.microsoft.com/en-us/kb/2344518 It will fix your issue.
Unfortunately, persistent columns are sealed meaning they cannot be deleted once created. You got 2 solutions (workaround) that you can try: Hide the column instead of deleting it and remove it from the view it was added. Create a new document library and copy all the documents into it (you can utilize the Open in explorer for easy copy/paste and use the ...
It doesn't seem like you are using OD for Business, but regular OD. I have an O365 E3 license, and my OD for Business menu looks different that what you've posted. I'm running Windows 10 x64 with Office 2016. OneDrive for Business menu: OneDrive menu:
Below given URL of that page from where the list is going to be created. http://serverURL/_layouts/15/new.aspx?FeatureId=%7B00bfea71%2Dde22%2D43b2%2Da848%2Dc05709900100%7D&ListTemplate=100&IsDlg=1 The number 100 for ListTemplate represents the type of the list you are creating. here given URL is used to create a custom list. If you want to ...
It seems you have used different master page for System master page and site master page.That is why it is coming different for both of them.
I tried the aforementioned solution mentioned at wowsomuch by saving the script as a file and linking it to a Content Editor web part on the page with the template links and found the following. It only works for me, sort of, in 2 of 3 scenarios: manual link : works * library web part : works * content query web part: does not work a window is displayed ...
You could try the Export-SPWeb and Import-SPWeb commands to export and import a library/list. They would basically export the data onto file system, and then import it back into SharePoint to the URL you designate. (And of course) Version history can be retained if you require. The syntax would be similar to below: Export-SPWeb -Identity <SiteURL> ...
Using PowerShell you can export the list and import it in new location. This will retain your history and versions. https://technet.microsoft.com/en-us/library/ff607895.aspx
Top 50 recent answers are included