I have a configured a retention policy on a document library, the document should be moved to another location (Drop Off library) after certain amount of time. This doesnt seem to be working.
Please note that I have configured the Content organizer feature and "Send To" connections in Central Admin. I also have changed the trigger time for Information Policy and expiration policy job to run every 2 mins and 5 mins respectively.
Am i missing anything, because the functionality is not working and there is no error being thrown. All i can see is that the retention action is displayed as completed in "Compliance details" tab after sometime, but documents havent moved to drop off library. Also other retention action such as move to recycle bin work perfectly fine.
Please help.
Thanks in advance
If Move to recycle bin is working but Transfer isn't, I'm assuming your destination site is the same as the source. If so, this is not going to work because according to Microsoft support
It was as per design. If you try to move documents to a different location using Retention policy, you have to move it a library in a different site collection. Preferably ‘Records center‘ site collection. Main idea of Microsoft is to have one Archival or Records center site collection for the whole organization.
So, if you are trying to move documents after expiration to a library in same site or site collection, you can use a workaround to start a workflow on expiration date which moves the document to archival library.
Hope this helps. Source
To start with for investigation
1.There are two timer job services in Sharepoint 2010 ( it looks the same on 2013 as well) so ... "Information management policy" and "Expiration policy". check if these Job are working as desired for the web application. I understand it works partially on some instances. But I don't know if it is on the same webapp level.
Next can you check if these documents are checked-out to some one on the team or to a person who has left the firm which is very common sometime User Profile service may give you tickle by not syncing as desired.
If you have custom content type for which the the document is saved. then if the same content type exist on the destination folder ( drop off lib) where document to be moved.
I had a situation when the documents where located inside a folder (leaf) inside document library. Move of document expected a same folder on destination which was weird. But after changing folder name which had '(' symbol it worked.
I have also seen some instances of permissions to the folder for the timer job but, I did not have that experience.
Without actual settings on the retention policy I can only give only pointers. Therefore, please give bit more information about the retention policy setup if it is not confidential.
I have similar problem, and after lots of try and error I found up that I have a required column in the destination content type which wasn't required in the source content type. Just check it!
Related
I have created an utility for browsing and uploading file from user's machine (OS is Windows10) to a SharePoint site's document library. This utility is created using 1. a canvas form created in Power App, 2. a workflow created in Power Automate and 3. destination document library of SharePoint site.
To briefly summarize about its working; when any user uploads any file using this form, workflow is triggered to store this file as an entry to a SharePoint list, and it is then sent to designated reviewers to get it reviewed and approved. On approval, file is moved from SharePoint list to another site's document library.
Files are successfully being moved to the destination document library.
Here is the problem I'm facing for the moved files - The document library has 'modified by' meta-data column associated with files. This field does not display actual user's name whoever uploads a file or replaces an existing file by uploading a modified version of this file. It always shows my name in 'Modified By' field.
Is there any way to fix this and show the actual user's name in this field who uploads any new file or replaces any existing one.
Any help is really appreciated.
Thank you.
The issue you are having is by design.
The kind of trigger you are using in SharePoint connector always operate in context of the owner of the flow (you)
Please check the following for detailed description and possible workarounds: https://sharepoint.stackexchange.com/questions/269396/microsoft-flow-always-run-in-context-of-user-who-published-it
You can try using 'update file properties'. I have not tested if this works or not, but it seems practical solution to test.
I am doing an in place search in a document library and results are being returned just fine. However, some users are reporting seeing the following message:
Some files might be hidden. Include these in your search
I also receive this message at random times for different searches. There seems to be reports of this on various boards with no real answer. Anyone know why this message would occur?
This may relate to the Search Service Settings > Content Source in Central Admin. Ensure that the addressers are correct and that the crawl have the same entry as you do. Normally you want to point the url to the default zone.
When done, reset the index and start a new full crawl.
I am supporting a Sharepoint 2007 site with a couple workflows associated with some document libraries. The customer wants files that have not been modified in 3 months moved to a specific document library automatically. Is there a way to do with with Sharepoint tools automatically, or do I have to create some kind of custom web part (if thats even possible for this)?
The recommended way to do this is to use the built in information management policies framework. Per list or document library you can setup scheduled checkpoints per item. At these checkpoints you can then "retire" an item, delete it or else archive it off to an archive list. Also, you can simply call a predefined SharePoint workflow to determine what should happen.
A typical example would be an information management policy that checks the list items weekly and calls a custom workflow upon then. You could then associate a workflow that checks the current item's modified date, check whether it's greater than 3 months and then simply move the item.
Have a look into the Share records management here
You can create a timer job. You'd set it up to run every day, e.g. The job would use CAML query to get old documents from the doclib and perform the move operation.
--- Ferda
In a live system, where we have never had trouble deleting alerts (its been up and running for about a year now), we have come accross this for one user on 2 particular alerts, the problem is we cannot delete either alert using any account (The users, my Admin accounts, the sharepoint installer account)- We get an access denied error. Now, the 2 alerts are set on the same document, which is held withing library X and to parent folders (X/FolderA/FolderB/Document)- After setting up the alert FolderA (And all its contents) were moved to a new library (Library z), and the alert stayed where it is, set up on library x - To my understanding sharepoint should've deleted it when it was moved?
We've tried the following;
Recreating FolderA/FolderB/Document structure in x
Cutting and pasting FolderA back into X (so it had the same Guids)
But we still could not delete the alert using any of the accounts :S Does anyone have any idea how we might be able to delete the aler?
I got this problem with one of my main portal site. I escalate ticket with Microsoft. After doing so many trouble shootings. Finally we created new web application with same name, host address and attached the content db.
Problem resolved.
I have a document library with a few files in it and I've noticed that doing a search for files in the document library (even the exact file name) does not seem to give any search results. The search does seem to provide results of terms within lists (such as Project Tasks) thought.
Does Sharepoint Services 3.0 index files within document libraries? I've gone into Advanced Settings of the document library -> Search and made sure the radio button is set to 'Yes' (it was 'Yes' by default).
The short answer is Yes.
The long answer will require some further reading as I can't remember how or where to set it up and of course there is always the chance you have it configured but it just isn't working.
OK, after doing a little digging around it turned out the Service Account and Content Access Account in SharePoint Central Administration > Operations > Services on Server > Windows SharePoint Services Search Service Settings were both set to the in-built user "Local System" which didn't have the permissions to fully index the site. What was odd was that it was indexing the lists but not the documents - I presume a different type of indexing operation is done on the two.
I created a new user on the server with the relevant permissions and assigned that to the Service and Content Access Account and within minutes I could see the Document Libraries within the search results.