![]() ![]() Make sure to make the IsDeleted column hidden. We're creating two separate columns because in SharePoint, it's the only way to track if a specific field just changed. Then create two yes/no columns, NeedsDeleted and IsDeleted. This is a process often used in databases where a table is given a Boolean flag named something like isDeleted, and then all views and queries only return data where that flag is false, and when a user "deletes" an item, the code just marks that flag "true", so the data never gets deleted, but behaves as if it has.įirst, create a custom permission level for users to retain contribute rights without delete privileges for this list. ![]() What you will want to do is implement your own "soft delete" process. If you trigger your Flow on item deleted, the item is already in the recycle bin by the time your actions run. You cannot hook an approval process to the delete process, and there wouldn't be any history to that either. When an item is deleted, the item and it's entire version history move to the recycle bin, and eventually disappear into oblivion. There is no such thing in SharePoint as "versioning for the delete process".
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |