If you or your admin knows PowerShell, you can use the SharePoint PNP library to delete the folder:
#if not already installed
#install-module sharepointpnppowershellonline #requires PS 4.0 or later.
Connect-PnPOnline -Url https://yourServer/sites/yourSite
Remove-PnPFolder -name Test -Folder "/shared documents"
You may see recommendations to ...
Try to use this
foreach (SPListItem item in list.Folders)
if (item.Title == "yourfoldername")
SPListItem newItem = list.AddItem(item.Folder.ServerRelativeUrl, SPFileSystemObjectType.Folder);
newItem["Title"] = "...
I finally found the answer I was looking for thanks to this Blog.
I deleted the CAML Query settings :
<FieldRef Name='FileDirRef'/><Value Type='Lookup'>SubFolder1</Value>
and added this line to my CAML Query Options ...
When you use BreakRoleInheritance with $true or $false you do the following :
you are assigning the folder with unique permissions.
Any new permissions added to the item are only applied to the item.
Only the difference :
$true to copy role assignments from the parent object to this object;
$false to assign only the current user to security roles.
So For ...
When you want to retrieve properties for a single item/folder/list/etc and not a collections of items/folders/lists/etc you need to specify properties like this:
ctx.load(list, 'Name', 'Url', 'other_property_here');
Basically, you DON'T use Include(), but specify the properties as comma-separated arguments in the ctx.load() function.
This question is primarily seeking opinions since there is no "right answer", but I'll give my thoughts:
Folders are OK. Even subfolders. Just watch your URL limits (and if using OD sync, your Windows Explorer or Office client limits).
Let users control how their data is organized and displayed, but offer guidance/best practices.
Don't require metadata ...
Rather than focusing on configuring the views to have a different view inside the subfolders than for the main library view, I think the easier path here would be to focus on getting the documents to inherit the metadata from the folders they are in.
This is very easily achievable if you use Document Sets instead of plain folders.
There are a number of ...
Folders vs. metadata is the age-old debate in SharePoint. We've been live in Teams and SharePoint Online for a few years now, migrated from a previous SharePoint 2010 server. The only correct answer is the one that works for your users and allows them to work efficiently. Here's points to consider before you set governance around this, based off my ...
First: Forget SharePoint Designer. It's a legacy product that was useful with on-premises installations, but will not do anything for you in SharePoint online if you are just starting out.
Second: This is a chicken and egg, never ending discussion. There is no one "best" way to organise files that suits every company or every individual. There will always ...
A CAML query may work. If multiple calls are ok then:
You can get a list of libraries using:
_api/web/lists?$filter=BaseTemplate eq 101
Note that 101 is for the Document Library template. A long list of template IDs here: https://techtrainingnotes.blogspot.com/2015/02/sharepoint-2013-list-and-library.html
And then from the list of libraries, get every ...
I found out for us where this error affects the Sharepoint Online web interface when we (admin) have an eDiscovery case open or litigation hold policy applied on the folder. It only happens on the web interface and you can delete the folder and all its sub-items if you deleted it through the OneDrive sync client or through "Open with Explorer" (IE only).
It's not best practise to make loads of folders and sub-folders. Consider other ways of structuring your documents. You mention '10 different project libraries' - what's wrong with this structure? It's easier to customise the security, since perhaps different project groups / departments need different permissions for each project?
Using multiple ...
If you have the option to change the approach to one document library per departement then the issue has been resolved as a Contributer can neither add or delete libraries.
Otherwise you will have to look into creating a new permission set where the delete option has been removed, but I think it will require a lot of maintanence to make that approach work
You can examine the returned XML to find related querries for your request...
There is no nice way to just pull the folder count, but you can use the /folders to retrieve all folders below the current node.
See this line from the returned XML for your query:
<link rel="http://schemas.microsoft.com/ado/2007/08/dataservices/related/Folders" type="...
Make them in to separate document libraries. Make one FINANCE document library and set user's permissions using Groups. Then make a separate FINANCE PLANNING AND ANALYSIS document library and again set user permission using Groups.
You'll need a naming system e.g. 'Finance 1' for the first finance project, Finance 1 for the next finance project - unless ...
You would be better served to not use folders. Utilize columns of metadata to categorize your items. Then create views of sub-sets of the content using filtering.
You can use Document Sets instead of folders in the root of the library. With a document set content type, you can set default content for the document set to contain when it is created. That should solve your first requirement.
For the permissions requirement, you can create a SharePoint Designer Workflow, and use the "List Item Permissions" actions to ...
You can do this by using Event receivers. Whenever a folder is created you have to check the level and send alert.
public override void ItemAdded(SPItemEventProperties properties)
//Once the item is added you have to check whether its folder or not
//if folder you have to check the level
Or you can try this approach which is using ...