Noel Williams

Anita Fritz

Implementing great designs for SharePoint and Teams

In this blog post we take a look at three designs that add real value to a Teams or SharePoint Online environment, note how implementing those designs is quite challenging and explore how software called MacroView Provisioner makes implementation so much easier.

Great Design #1

You are using Microsoft Teams extensively. You have tried using the email addresses of Teams libraries to streamline the saving of outlook emails, but have found that approach leaves a lot to be desired. You want instead to use software like MacroView DMS so you can drag and drop to save Outlook emails. As part of the save the MacroView software will automatically select an email content type and record the attributes of the email in corresponding metadata columns. So you need to add that email content type and its metadata columns to the Teams library. You also want a new emails view added to the Teams library, so you can view the saved emails together with their attributes – just as you would in Outlook itself. This design will make it easy to save emails while you work in Outlook, and also allow the saved emails to be visible within the Teams UI.

Great Design #2

You want to manage documents and emails related to lots of projects in SharePoint Online. It is essential that you be able to search for those documents and emails using project attributes such as project type, project start date, project manager, etc, but you don’t want to be prompted to enter those project-level attributes every time you save a document or an email for a project. You have decided to use a document set for each project, with the project document set content type having a number of project-level attributes, which are then Shared with the documents and emails that are subsequently stored in the project document set. You also want to set these shared metadata attributes to hidden in the document content types within the document set – that will ensure that you are not prompted for these project-level attributes as you save documents and emails.

Great Design #3

You are migrating a large Public Folder environment to SharePoint Online. To avoid list view threshold issues you have decided to create a tree of sites and libraries, ready to receive the migrated emails. It’s a large Public Folder structure, so there are over a thousand libraries to be created, each with the email management content type, metadata columns and emails view that are described above under Design #1. Oh, and your users want to see standard sets of folders in those document libraries, with different sets of folders across the different libraries. Having that design in place is a key success factor for the migration – the new SharePoint Online environment needs to look and feel similar to the existing Public Folder structure, otherwise users will be reluctant to adopt.

Implementing such designs is challenging

Implementing such designs is challenging indeed if you are using the native site settings and library settings pages of the SharePoint UI. SharePoint best practice is that you define site columns and site content types (at site collection level) with the site settings page and then incorporate those components into your document libraries with the library settings page. You also need to use the library settings page to define additional views.

The challenge with Design #1 is that you need to add components to the shared documents library in each Teams site. Users can create new Teams sites quite often, so this library enhancement task is going to chew a lot of admin resources.

Design #2 is challenging because of the number of admin steps involved. Adding document set content types and columns at site collection level is not a frequent task, but for every new library you need to remember to set the hidden columns and define the views.

Volume is clearly a challenge with Design #3, but so too is the need to create different sets of folders in the 1,000+ new document libraries. Clearly this is not a design that you can create manually using the native admin features of SharePoint Online.

MacroView Provisioner

MacroView Provisioner makes it much easier to accurately implement designs in SharePoint and Teams, such as the three example designs outlined above.

MacroView Provisioner complies with SharePoint best practice by the way it adds content types and metadata columns at the site collection level, and then re-uses those components in document libraries. It supports document sets well, including the definition of Shared metadata columns. MacroView Provisioner is also aware of SharePoint peculiarities, such as the need to define hidden attributes at library, rather than at site content type level. This means that it is ideal for implementing Design #2.

MacroView Provisioner can create new site collections, sites, libraries, document sets and folders in SharePoint – both SharePoint Online and on-premises SharePoint. It can also add new design components to existing site collections and libraries. So you don’t have to start again when you want to implement a great design.

The software has excellent support for provisioning Microsoft Teams. In addition to adding new content types, metadata columns and views to the shared documents libraries that are created automatically by Microsoft Teams when you add a new Team, MacroView Provisioner can also create a new Team site or a new channel within an existing Team site. It recognises that Team sites have a single document library, so it allows you to add components to a Teams library in a single step.

Once MacroView Provisioner is installed, you can right-click on a site collection, site or document library in the intuitive MacroView tree-view of your SharePoint environment and choose provision in order to add new design components or create new sub-areas. This means that users with appropriate permissions can create and extend designs while they continue to work in the familiar environment of Microsoft Outlook or Word, Excel, PowerPoint or DMS Explorer.

Behind the scenes, MacroView Provisioner makes good use of Microsoft PNP – the de-facto standard for defining SharePoint provisioning in XML files. MacroView has augmented the standard PNP offering so that its users benefit from additional provisioning functionality and much improved performance when provisioning.

MacroView Provisioner dramatically reduces the need for administrator effort (compared to using the native Site Settings and Library Settings pages) while at the same time ensuring accurate, consistent designs.

This video shows MacroView Provisioner in action.