Skip to main content

Microsoft SharePoint and Dynamics CRM -- Better Together: Part 1

This blog is an excerpt from an InfoStrat white paper

We often are asked which tool is best for a particular application: SharePoint or Dynamics CRM? 

I will devote a series of blog posts to this topic. 

The short answer is that it depends on what problem you are trying to solve.
SharePoint and Dynamics CRM were developed independently, with different features and functions in mind.  SharePoint began as a document management and collaboration environment, combined with a search engine.   It was not originally designed to provide line of business applications which rely on relational data as many line of business solutions require.  SharePoint has over the last few versions increased its capabilities to handle structured and external data.   

Dynamics CRM began as a line of business solution for sales force automation and customer relationship management. At the heart of its paradigm is a shared, relational database with an integrated front end, reporting tools, a sophisticated security model, and data integrity features. It does not provide a web search engine, document management, portals, and collaboration capabilities that are inherent in SharePoint.

SharePoint and Dynamics CRM have many architectural features in common, such as:
·         Web-based, with broad browser support
·         Use SQL Server to store data and metadata
·         Integration with Outlook and other Office products
·         Allow single sign-on with Active Directory
·         Rely on Windows Server
·         Built on Internet Information Server (IIS)
·         Allow documents to be stored
·         Use Windows Workflow for automating workflows
·         Use Visual Studio as development environment
·         Support security groups

Much of the user interface and some of the administrative functions are similar for the products, as one might expect from their integration with Microsoft Office.

Popular posts from this blog

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun