Like Dynamics 365 and the Power Platform, SharePoint has always been a platform to define data and create applications.
However, SharePoint suffered from different ways of implementing requirements and having an API which was much more ‘multi-headed’ than the simpler and debatably stronger Dynamics API.
SharePoint had and has the Server-side API, the Client Object Model, and the REST API working alongside Custom themes, web parts and applications – whereas Dynamics 365 had simplified supported ways of handling customisations, a single API until OData and REST, and a core model for handling plugins.
This made Dynamics a (very debatably) better platform for building and deploying business applications, and ultimately lead to aspects of Dynamics growing into the Power Platform.
However, the SharePoint Team have not been idle, and this has changed in recent years.
Old style team sites still exist in SharePoint, but these have been replaced with newer communication sites that have a common user interface and supported ways of customisations.
This changes SharePoint from a develop-first platform to a supported-customisation-first platform in a similar fashion to Dynamics; and so provides a more robust way of working – this combined with SharePoint’s web parts for news and content as well as standard documents and Links makes SharePoint a much stronger and supported application for Intranets and collaboration.
(Particularly given the link up with Microsoft Teams but that will be the focus of another article!)
Figure 1 – Building a Page in SharePoint with out-of-the-box Web Parts alongside Custom Web Parts in the App Catalogue built via SharePoint Foundation
This ability to use SharePoint as a user-first application instead of a IT-first development platform enables better content management and so a higher level of engagement and user adoption.
Microsoft define this new approach and their reasons for the changes between ‘old-SharePoint’ and ‘new-SharePoint’ here: https://docs.microsoft.com/en-us/sharepoint/dev/solution-guidance/portal-branding
This can be improved with data models built using SharePoint lists to combine good content management and presentation with the custom data we track in lists.
This starts for Intranets and collaboration – but can then grow in different ways.
With the advent of the Power Platform, we can embed Canvas applications in SharePoint to connect users to our bespoke apps – and we can also use SharePoint lists as the datasource for these Canvas apps.
This can be a very powerful way of delivering smaller lightweight apps at a lower Canvas app License cost, and then making easily accessible via our SharePoint Intranet or a Microsoft Teams tab.
Figure 2 – Using a SharePoint Page to host a simple Canvas App showing a Contacts List from Dynamics
This can be a very powerful way of delivering smaller lightweight Apps at a lower Canvas App license cost, and then making easily accessible via our SharePoint Intranet or a Microsoft Teams Tab.
What does this mean?
- We have more opportunities to use SharePoint as an application and use supported development techniques that are easier for future support.
- SharePoint is much more integrated with the Power Platform for a common approach to business logic.
What benefits does this give us?
- We can implement an IT strategy in the Microsoft Cloud that uses the best elements of SharePoint-for-content, Teams-for-collaboration and the Power Platform for Apps; without having to worry about specific Dynamics Projects vs SharePoint Projects – the Cloud is now much more of an integrated platform.
- We can engage our Teams and stakeholders much better with our content and Apps.
- We have easier and better supported methods of creating content that reduces the risk of ‘dead intranets’.
How do we do it?
This article focuses on the architecture of SharePoint and how this works in the modern Microsoft Cloud.
We can put this architecture to use in the following ways:
- PowerApps Consultancy – Create strong Line-of-Business Apps which we can then integrate into Teams and our Intranet
- SharePoint Consultancy – Define good Content and Lists within our Intranet
- SharePoint Development – Use the SharePoint Foundation to develop new Web Parts for SharePoint that can act as in-SharePoint Content Presentation or Mini-Apps
At CRMCS, we focus many of our articles on how to build PowerApps and Dynamics.
Our DocDrive365 IP focuses on how to engage SharePoint content, specifically documents and Metadata, within Power Apps and Dynamics.
This series of articles in our monthly newsletter is going to look at how we develop new web parts in SharePoint that can help us integrate Dynamics and DocDrive365 into our Intranets – so we can start thinking of SharePoint, Teams and Dynamics as a single solution for business; and not lose the benefits of these Applications when a business or partner only focuses on Dynamics or only focuses on SharePoint.
Hopefully this article has given a good feel for what is possible.
Our next article will take a deep dive into how to develop a SharePoint Custom Web Part using SharePoint Framework (SPFx) – taking the basic HelloWorld example and making applicable to our world of Power Apps by integrating Dynamics Data into the Web Part.
We will then look at integrating Documents between PowerApps (what a document ‘regards-to’) and SharePoint to give a consistent information map for finding good information quickly.
Why the SharePoint Framework?
Introduction to Modern SharePoint Web Parts for Page Design
Branding Guidance for SharePoint Online Portals