New answers tagged

1

SharePoint is simply hiding the view files and the template file for you in usual GUI mode, as there is no reason for them to be visible in a document library. In Explorer View however, everything is visible, including the Forms folder, view files and template file.


0

Ok, i found the solution myself so i will answer here. The problem was that the folder was created as the "custom_document_set" content type that we are using in our environment instead of "folder" document set which should get applied when creating a folder. It happens during the site creation script that we have which causes the folder to retrieve the ...


1

Another option could be a content query web part. You can configure the web part to get documents from your library and apply condition to show recently modified documents. You can point web part to a document library in parent site or even in sub site. This web part is also OOTB web part.


0

You must use JSLink instead of inline scripts. JSLink is providing us a method to customize column rendering, and you could easily add the expected behavior: Sample: // Create a namespace for our functions so we don't collide with anything else var customFunctions = customFunctions || {}; // Create a function for customizing the Field Rendering of our ...


0

Check your sites Recycle Bin. If there is nothing there, check the Site Collection recycle bin. Typically if its less than 30 days since deletion, you can restore if from one or the other. If they are in neither of these, I recommend you restore from Backup. Rule of thumb during any migration: Don't delete from the source, until the customer confirms ...


0

Any changes to files should show up in the Change Log. There should be an add event when the file was created. You can either write some code or use PowerShell to read out the log. The log would also tell you if the file was deleted or moved after you moved your content.


0

I think that OfficialFile.asmx requires the document routing feature to be enabled on the receiving site, try enabling the Content Organiser feature on the SPWeb.


0

With a combination of help from the answers from @Mike and @Jordan, I was able to resolve this issue. The "Lots of People" is coming from the highest level of permission inheritance. I figured this but didn't know how to configure that highest level. Using the "Check Permission" on a specific site, I could see that users "None" listed as the Permission ...


1

You could make a separate list (i'd use a discussion board) that ties to the document library through a lookup column to allow users to make comments/questions on a specific document. This separates the concerns of users having access to edit documents that they don't need to edit.


3

You could require content approval and turn on track changes. (In Word 2013, you can require a password to turn off track changes.) Then the person who has to approve the document can accept or reject individual changes once the document comes to them. Or, there's a "collect feedback" workflow that will route a document for comments.


3

Based on your diagram it looks like you are inheriting permissions from the top level site. If you build out a sub site in a site collection one of the options on creation is whether or not you want to use the same permissions groups from the parent site. If you select Use unique permissions you will be able to create and define the members of those ...


2

Sounds like you need to do an audit of the entire implementation. I'd sit down with users that are the owners of the data, or department head, etc. and get a good idea of who will be using the site. You can also do a little preliminary work and grab some AD groups to verify that everyone in that group will be using the site, so they won't have to list out ...


1

Add People/Group Column to your library While adding documents or folder add person who needs to access that particular folder/document Write a workflow on Document library to impersonate permission of every item using people/group column This may help you to automate the document sharing. Also you can use Power shell script instead of workflow.



Top 50 recent answers are included