Advertisements

The “New item” menu in modern SharePoint document libraries now allows adding templates

I happily stumbled across an update to modern document libraries I hadn’t noticed before. The modern document library “new item” menu now includes an option to “Edit New Menu” which pulls up this pane in-context: And also includes the ability to upload a new template directly from the menu, rather than through content type settings.…

Advertisements

5 ways you can use SharePoint list and library view settings to improve the user experience

SharePoint has many out-of-the-box (OOTB) ways to improve the way data is displayed in lists and libraries. Many of these can alleviate headache your users experience when adapting to a new way of working with their abundance of ever-growing information. Let’s check out a few things you can do right now, in less than five minutes:

  1. Prevent horizontal scrolling by carefully selecting displayed columns
  2. Sort items appropriately
  3. Filter to relevant info per view
  4. Group items into logical “buckets”
  5. Adjust item limits

10 reasons putting team/department documents in SharePoint is better than shared drives: Part 2

Asset 1mazeThis post is a continuation of 10 reasons putting team/department documents in SharePoint is better than shared drives.

See part one for information about:

  1. Version history
  2. Approvals/Administration
  3. Check-in/Check-out
  4. Co-editing
  5. Archiving & retention

And below for information about:

  1. Sharing and security
  2. Remote access
  3. Metadata and views
  4. Workflows & alerts
  5. Sync & export

10 reasons putting team/department documents in SharePoint is better than shared drives: Part 1

Asset 1mazeYou 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 you don’t need it anymore. But managing team/department documents on traditional shared drives has challenges like this all the time, with management, retention, content ownership, etc. SharePoint, however, can greatly assist in keeping your content current, relevant and organized.

Of course making the switch from shared, common network drives to SharePoint can be intimidating. But the benefits of doing so are well worth the effort to make your team work more efficiently. This post will highlight 10 features in SharePoint you can’t necessarily get from shared network drives:

Part One:

  1. Version history
  2. Approvals/Administration
  3. Check-in/Check-out
  4. Co-editing
  5. Archiving & retention

Part Two:

  1. Sharing and security
  2. Remote access
  3. Metadata and views
  4. Workflows & alerts
  5. Sync & export

The “Edit” icon column: a SharePoint essential for all lists and libraries

Asset 2edit

Yesterday in a SharePoint 200 session I gave at Lawrence Memorial Hospital, I shared one of my favorite SharePoint “nuggets” which is the “Edit” icon available out-of-the-box, and easily added by any level of user in just 4-5 steps.

This edit icon column can be added to any list or library view in SharePoint and allows you one-click access to edit the properties of a document or edit a list item or form. In addition to that it’s security-trimmed, meaning only people who have edit/contribute permissions will actually see the icon at all. Everyone else will only see an empty column.

To add the column, you must have the ability to create or modify views and list settings.

Note this is only available in classic view lists and libraries. In the O365/Modern experience you can simply select an item, click “Edit” and the right edit pane appears to allow a similar experience.

Convert SharePoint documents to PDF automatically using Microsoft Flow

convert.PNG

We’ve been waiting a lifetime (dramatic?) for this feature. And now it’s here! Sort of.

Currently, with a new “Preview” action release in Microsoft Flow, we’re able to convert documents to PDF in OneDrive for Business via workflow. While this isn’t ready for SharePoint yet, we can make it look that way for our end users. Basically:

  1. When a file is created or modified in SP
  2. Create document in OneDrive for Business
  3. Convert document
  4. Create document in SP

It’s roundabout but we get exactly the result often requested: convert SharePoint docs to PDF automatically. Here’s how to set this up. A video walkthrough is available at the bottom of this post.

SharePoint workflow that creates a document based on a template

Outcome:

process

docoutcome

Intro:

Look at that workflow above – have you ever seen something so beautifully simple? I’m excited to share several solutions with you in this one post. This post should cover the following:

  1. Working with content types
  2. Creating a template for each content type capable of having merge fields
  3. Finding a way to merge list item info into a new document via workflow
  4. And if you’re super ambitious, expanding the workflow just a bit with an if/then statement to use different templates based on conditions in your list

But because this is a massive topic and could be tailored an infinite number of ways, I encourage you to comment or tweet me for additional guidance more specific to your scenario. So here we go!