Tag Info

New answers tagged

0

Try this PS snippet: $foldersColl = $oList.GetItems($folderquery) foreach($folder in $foldersColl) { $folder["Created"] = $dateToSet $folder.Update() } Updated answer (after reading comments) Add-PSSnapin Microsoft.SharePoint.PowerShell $web = get-SPWeb "http://portal/"; $list =$web.lists["Documents"]; $folderName = "BNFSDocs"; $item = ...


0

Could be please confirm what really is the issue? I would like to assume its the error you receive in trying to create a new folder on your document library. In that case please visit advanced settings->Make New Folder option to yes. Hope this is what you were looking for !!


0

have you tried to use workflow for this? Everytime you want a new folder you would start a workflow, enter a name of the project and then workflow steps would create main folder, subfolders and set permissions?


1

As per MSFT the limit of items in a Library (including folder) is 30M, that's mean if you have the 1 folder in your document library that can contain upto 30M items. But real Catch is the List View Threshold, which is 5000 items per view( you can change it on prem). So if your library having more than 5K items then you have to filter the items in a way that ...


0

The answer directly from MS: Documents - 30,000,000 per library - Supported You can create very large document libraries by nesting folders, or using standard views and site hierarchy. This value may vary depending on how documents and folders are organized, and by the type and size of documents stored. Software boundaries and limits for ...


0

Go to Library Permissions. Stop Inheriting Permissions. Remove All Permissions. Grant permission to your Group which has Contribute Permission. Also, check the Toolbar Type of the Library Webpart. Ensure that it is 'Full Toolbar'.


0

SharePoint List does not have folders, Document Libraries does. As an Example: using (SPSite oSite = new SPSite("url")) { using (SPWeb oWeb = oSite.OpenWeb()) { SPDocumentLibrary oDoc = oWeb.Lists["list_name"] as SPDocumentLibrary; int numFolders = oDoc.Folders.Count; if (numFolders > 0) { ...


3

Set the DocumentSet.Folder.Item.ProgId to "SharePoint.DocumentSet". Right now it will be empty. See this for more information: http://www.sharepointnadeem.com/2011/08/sharepoint-2010-document-sets.html UPDATE Here is the sample PowerShell code. I haven't however tested it: $web = Get-SPWeb http://yoursite $list = $web.Lists["YourList"] $docSetName = ...


0

You can disable the "New Folder" button in Library Settings - Advanced Settings - Make "New Folder" command available?. This does not stop a user from opening in explorer view and creating folder there, like you had mentioned. As far as permissions on the library go, contribute to the library gives them access to create new documents as well as new ...


0

A bit late on this so it's probably answered. But just in case... How much content do you have in that library? If it's only a little bit, just create the new library and folder by hand, download the docs from the current lib and upload to the new lib using upload multiple. If it's a lot of content: If you don't have publishing enabled: save the library ...


0

You can use event receivers. But it's not a good idea. Why users shouldn't be able to remove folders? If you want to create good structure, you should look to Taxonomy/Metadata feature. You can find a lot of articles with Folders/Metadata comparison. For example: ...


0

If you find that permissions are not the issue, I found a way to add it back in: Go to the library Click "Site Actions" in the top left and then "Edit Page" In the library webpart, click the drop down and select "Edit Web Part" Check "Toolbar Type" in "List Views" If "No Toolbar" is selected, change it to "Full Toolbar" If "Full Toolbar" is already ...


1

For 2) you can create a custom permission level - contribute but not delete. Assign that to folders 1 & 2. Should work as required


1

If I understood your requirements correctly, the only way to achieve this is with an event handler. This will require some development effort as it is not possible with the OOTB features of SharePoint, however it is really easy to accomplish.


1

You can definitely do this by breaking the permissions of your subfolders. If you set Folder 1 and 2 to view only you can then open the subfolder and break the permission inheritance from the ribbon. You can then grant access to users or groups at the appropriate access level (Contribute should do it). Updated your diagram below. Root |---- Folder 1 ...


0

This behavior is by design. This behavior corresponds to user's experience on Windows file servers or when users access to a SharePoint web server through Explorer View (WebDAV HTTP protocol extension). Here is the MSFT KB Article on this issue. Contributor users are not able to rename items in SharePoint if the Delete permission level is removed from ...


1

The user must have delete permissions to rename files/folders. Reference: https://sharemypoint.wordpress.com/2007/12/21/cannot-rename-file-if-you-dont-have-delete-permission/


0

Don't give them contribute rights to the site, just to the libraries you want them to edit.


4

The problem with the folder name "large_files" is that it ends with the string "_files". This is a reserved name for SharePoint Online. Scroll down here http://support.microsoft.com/kb/905231 and you will see that extension listed, amongst a number of others. For a list of reserved/blocked characters in SharePoint Online check this link ...


0

By default each folder or SharePoint element (site, list, library etc..) will inherit permissions from its parent even if the parent broke the permissions from its own parent. So Level 2 will keep inherting permissions from Level 1, so you don't need to do any extra work for it. There is nothing wrong going in this approach. You might also consider document ...


0

Your Level 2 sub folders will automatically inherit from your Level 1 folder. It is up to you if you want to break the permission inheritance at each Level 2 subfolder. That is also possible. However, my general recommendation to clients is not to establish folder level permissions since it is very difficult to manage with the out-of-the-box interfaces in ...



Top 50 recent answers are included