InfoStrat's Townsend Report

In an earlier post, I discussed the possibility that you may need fewer reports in Dynamics CRM than you might think. 

This is because Dynamics CRM offers several approaches to get data out of the system which were served by reports in a traditional database application. 


Approach Comments Skills Needed Dashboards Great way to get the big picture and combine multiple data items on one screen End User Advanced Find May be saved as personal views or shared with other users End User Export to Excel Starting point for further manipulation

SharePoint Strengths This post focuses on the strengths of SharePoint. This blog post is an excerpt from an InfoStrat white paper. 
Portal FrameworkSharePoint provides a framework for building websites, whether public websites, intranets or extranets.You can create and populate a website quickly with SharePoint with a minimum of custom development.

Data Models in SharePoint 2013
The Microsoft Office Dev Center provides a thorough explanation of developing applications for SharePoint 2013 (https://msdn.microsoft.com/en-us/library/office/jj162979.aspx). The article on what’s new for developers (https://msdn.microsoft.com/en-us/library/office/jj163091.aspx) highlights the key enhancements of SharePoint 2013 for developers and system architects.

The enhancements are in the following areas: ·Cloud App Model
·Familiar programming model using web standards
·Development tools
·Core platform enhancements
·Mobility
·Social and collaboration
·Search
·Workflows
·Enterprise Content Management
·Bus…

Dynamics CRM Strengths

This post focuses on the strengths of Dynamics CRM -- the next in the series on the strengths of SharePoint. This blog is an excerpt from an InfoStrat white paper. 
Relational DataWhile SharePoint’s strength is unstructured content such as documents and web pages, Dynamics CRM is often better for structured, relational data.SharePoint provides some features to get you closer to relational behavior, such as lookup columns in lists and site columns, but other key relational features are missing.

Several years ago my company embraced SharePoint for generating customer proposals.It was great to store drafts, collaborate on documents, and track calendars.We added metadata to the document library to show the type of proposal, name of customer, and other pertinent information.
We ran into problems, however, when we want to run more sophisticated reports on sales activity, to match security permissions to account territories, and other features that are common in a CRM s…

SharePoint is a content management system with a portal framework, a search engine and document management. It is a general purpose collaboration tool and may be applied to intranets, extranets and public websites.SharePoint is based on the concept of lists, which are comparable to database tables. Lists are used for a large number of SharePoint features such as calendars, document libraries, content lists, news items and more.Lists may be easily created by end users within their sites, and they do not have to be centrally managed so that these lists may differ from one site to another in a SharePoint implementation.
Dynamics CRM is a database application for tracking a number of entities relating to sales, marketing, customer service and contracts along with related activities and workflow.Dynamics CRM exposes the data model to administrators as entities and attributes (tables and columns).They can easily view all entities and attributes, as well as all locations such as forms where …

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