This post is a continuation of 10 reasons putting team/department documents in SharePoint is better than shared drives. See part one for information about: Version history Approvals/Administration Check-in/Check-out Co-editing Archiving & retention And below for information about: Sharing and security…
You know that one file, right? The one named "Agenda.docx" in the folder called "November" in the "2008" folder in another folder called "DO NOT Delete" in the "Archive" folder of the "Retired Committees" folder? Me either. And chances are…
Currently, with a new "Preview" action release in Microsoft Flow, we're able to convert documents to PDF in OneDrive for Business. While this isn't ready for SharePoint yet, we can make it look that way for our end users.
Learn to automate item-level permissions by creating a 2010 SharePoint Designer workflow with an impersonation step.
This post covers one solution in which a 2010 SharePoint Designer workflow errors out due to invalid e-mail addresses.
When a user tries to edit a document from SharePoint using the client (not Edit in Browser) the client opens to a blank, gray background (no document) or doesn't open at all. Other times, it opens but as read-only. This post suggests solutions to these issues.
When using major and minor versioning, you could run into a situation where you wish to create major versions of all documents so that all are published and visible to all permission levels.