Timeline for Deleting all the items from a large list in SharePoint
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 18, 2022 at 15:07 | comment | added | Code Pope | If you have workflows which are dependent on fields of this list, then they will be broken and must be recreated. | |
| Jul 7, 2017 at 12:08 | comment | added | pholpar | @DennisG: Saving a list as a list template does not include permissions. Exporting the list via Export-SPWeb -IncludeUserSecurity (you can restrict the export to your list via -ItemUrl "lists/YourList") "preserves the user security settings except for SPLists that have broken inheritance and item level permissions set", but the list will be re-created using a new ID, so lookup fields referencing the list will be still broken. | |
| May 25, 2017 at 16:04 | comment | added | Mike | I came here to suggest the template option without content. That seems like it's at least worth a shot before running some code. | |
| Jan 10, 2012 at 12:24 | comment | added | Dennis G | @AlexPoint & omlin both correct. Saving the list as a template should take care of columns, views, permissions etc. - but sometimes it doesn't work, so I would first try it out before deleting the old list completely. | |
| Jan 10, 2012 at 12:02 | comment | added | AlexPoint | Would it help to save the list as a template and NOT include the content? That should save the columns and views and permissions and so on... | |
| Jan 10, 2012 at 11:42 | comment | added | Andrey Markeev | This approach is definitely acceptable in some cases, but you should take into account, that the lookup fields, which point to the deleted list, will be broken. Also, all the list views will be removed from all pages and from all sites. | |
| Jan 10, 2012 at 11:20 | history | answered | Dennis G | CC BY-SA 3.0 |