Deleting a large SharePoint library with retention labels applied to content
Are there any clever methods known to anyone for deleting a large SharePoint library that has retention label applied to all its content? I understand we will have to individually delete each item to empty out all folders before any folder and ultimately the library can be removed. Any other ideas?Calling all experts in retention labels!!!!
Hello experts, For those who are guns with retention policies and labels I have a challenge for you! In all scenarios I have encountered I can clear a retention label from a document, then delete. This is a problem - in my environment a document always needs a retention label. Context: I operate in a heavily regulated environment, all documents created/uploaded in SharePoint Online are considered records, and require a retention label to be applied (a 'record' requires disposition, thus requiring the retention label). There are different types of records; so there are multiple retention labels published to a location (two are published through a retention label policy, and the default label is done through an auto-apply retention label policy). If I clear the retention label from a document then delete, the document sits in the preservation hold library with no retention label (the auto-apply policy does not 're-label' the document in that location later) - this is a problem. If I create a document, then delete it before the auto-label policy labels the document (up to 7 days), the document sits in the preservation hold library with no retention label (the auto-apply policy does not label the document in that location) - this is a problem. I've tried using a published label as the default label for the document library (via library settings > Apply label to items in this list or library) - I can still clear the label (the option is available when more than one label is available - see below). How can I ensure a retention label is always applied to a document (AND have multiple retention labels available for selection)???? Any insights appreciated.Teams Shared Channels - SharePoint Search Limitations
Good Day All, I am currently working on a project for migration content from File Server to SharePoint / Teams. We have decided to test Teams with shared channels for some of the data types and quickly realized that SharePoint search doesn't index the custom columns (metadata) added to shared channel sites and therefor they aren't added as crawled properties on SharePoint search schema which we then cannot add to RefinableStrings. I have compared a shared channel site vs traditional site where this is working and cannot seem to find differences in search configuration or any features. Is this a bug or by design?
Disposed items not appearing in Purview portal for records management
When I done with the disposition process under records management, but disposed items not appearing in Purview center. Always it is showing as "Failed due to load data. Please try again later". Even after disposition process document is still appearing in SharePoint library (appearing even after 96 hours). What could be the potential reason for this kind of behavior.
SharePoint Retention - How have you applied it?
Hi all, I'm starting to look at retention in SharePoint. Currently using SharePoint as a document management system (replaced our drives) and one of the benefits was to utilise retention to avoid hoarding documents going back 20 years! So it would be great to hear how you have applied it and experiences with it: do your organisations staff have to manually tag the document or have you automated the retention label based on content type? do you have just the standard - after x years delete. Or do you have a review, i.e. untouched documents after 18 months will be pinged to the owner to confirm whether it should remain (and then stay for the remaining retention period) or whether it's no longer needed and can be deleted? Looking forward to hearing others experiences!Records Retention Time Limits
Hi, In GCC High - Records Management - File Plan - We are importing using the provided template. The import was rejected showing the error "RetentionDuration. Error. The value of RetentionDuration cannot be larger than 24855" Is this a limit of the file import function or is this a limit of GCC High Records management. Not a big issue per se. 24855 (a wee bit over 68 years) should cover almost all non-permanent records. However, some orgs that work with hazardous materials or environment issues have record retention rules that require 75 years or more. Finally, curious to know why 68.0958904109589 years is the max retention. It is a unique number 🙂 Thanks! Chuck Piotrowski
