Skip to main content

Blog Posts on Dynamics CRM v SharePoint

For years, there has been a lively debate in the Microsoft developer community about which scenarios call for SharePoint, Dynamics CRM and custom development.  Microsoft has added features in each version which create more overlap, and bloggers have approached the topic from different perspectives.

In addition to my blog posts here and the InfoStrat white paper.  I would like to highlight some of the posts from others in the community.

Robert R. Freeman, in his blog post CRM and xRM vs SharePoint: Business Solution Architecture, offers characterizations of both Dynamics CRM and SharePoint, and leans toward SharePoint for general purpose office solutions but CRM when CRM-specific functionality such as email outreach or contact management are required.

The SharePoint Blog post Compare Microsoft CRM vs Microsoft SharePoint written by Scott Mangelson similarly calls out SharePoint for portals and unstructured data and CRM for front office business processes based on structured data.  This post is repeated nearly verbatim on the CRM Software Blog as Microsoft CRM vs. SharePoint: Why One Over the Other?.

Another post on the CRM Software Blog Microsoft Dynamics CRM and SharePoint focuses on the benefits of integrating SharePoint with Dynamics CRM.  An older post on integrating SharePoint and Dynamics CRM appeared on CRM Solution Comparison with the title Microsoft Dynamics CRM vs SharePoint. It includes this video which speaks to choosing between SharePoint and Dynamics CRM. 

To read more, see the InfoStrat white paper

Popular posts from this blog

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

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

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