Skip to main content

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

This blog is an excerpt from an InfoStrat white paper

SharePoint and Dynamics CRM are based on different paradigms, and some but not all of their concepts map to one another.

Element
Dynamics CRM
SharePoint
Data
Entities (relational data)
Content types (pages, lists, etc.)
Fields
Attribute
Column / field
User Interface
Not applicable
Web parts
Data entry
Forms
Web pages
Knowledge Base
Knowledge Base
Wiki
Workflow
Workflows
Workflows
Views
Reports, views
Views, content query web part
Web sites
Not applicable
Sites and sub-sites
Web site templates
Not applicable
Site templates
Web page templates
Not applicable
Page templates
Dashboards
Dashboards, web components, charts
Web part pages, Business Data Catalog
Forms
Multipage form (tabs, one-to-many)
Single page form
Personalization
My Work
My Site
Notifications
Workflow
Alert
Tasks
Tasks
Tasks
Duplicate checking
Duplicate checking
Document names
Reports
Report designer
Report Center; Excel Services
Advanced Reports
Report Builder (SQL Reporting)
Report Builder (SQL Reporting)
Offline
Offline (requires Outlook)
Offline (requires Groove)

Table 1. SharePoint and Dynamics CRM Key Elements

Both SharePoint and Dynamics CRM are integrated into Microsoft Office in several ways.  For instance, SharePoint allows saving documents from Office into SharePoint document libraries, as well as linking to Outlook Calendars.  Outlook meeting requests can link to SharePoint workspaces.  Office programs include SharePoint functions in the ribbon interface.
Dynamics CRM (with the Outlook add-in) allows Outlook contacts, email messages, and appointments to be quickly added to Dynamics CRM.  Dynamics CRM records can even be taken offline in Outlook or viewed in mobile apps, a great feature for field workers.

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