<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Microsoft Dynamics CRM or SharePoint</title>
	<atom:link href="http://www.powerobjects.com/blog/2009/04/29/microsoft-dynamics-crm-or-sharepoint/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.powerobjects.com/blog/2009/04/29/microsoft-dynamics-crm-or-sharepoint/</link>
	<description>Bringing FOCUS to Dynamics CRM</description>
	<lastBuildDate>Thu, 29 Jul 2010 19:05:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Dean Jones</title>
		<link>http://www.powerobjects.com/blog/2009/04/29/microsoft-dynamics-crm-or-sharepoint/comment-page-1/#comment-1052</link>
		<dc:creator>Dean Jones</dc:creator>
		<pubDate>Tue, 19 May 2009 14:26:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.powerobjects.com/2009/04/29/microsoft-dynamics-crm-or-sharepoint/#comment-1052</guid>
		<description>Deon - I agree with your basic position, but your comment that SharePoint is not only about data, goes on to point out it brings together people process and information. I would argue that everything you list is data, structured and unstructured. 

I&#039;m not saying CRM and SharePoint do not work well together. They do. I&#039;m point out that CRM has relationships. It allows you to relate contacts with accounts, cases with contacts, projects with accounts, invoices, hours etc. 

My point of this blog is to get organizations to look at how they use the different solutions, and the pros and cons of each.</description>
		<content:encoded><![CDATA[<p>Deon &#8211; I agree with your basic position, but your comment that SharePoint is not only about data, goes on to point out it brings together people process and information. I would argue that everything you list is data, structured and unstructured. </p>
<p>I&#8217;m not saying CRM and SharePoint do not work well together. They do. I&#8217;m point out that CRM has relationships. It allows you to relate contacts with accounts, cases with contacts, projects with accounts, invoices, hours etc. </p>
<p>My point of this blog is to get organizations to look at how they use the different solutions, and the pros and cons of each.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deon Taylor</title>
		<link>http://www.powerobjects.com/blog/2009/04/29/microsoft-dynamics-crm-or-sharepoint/comment-page-1/#comment-1051</link>
		<dc:creator>Deon Taylor</dc:creator>
		<pubDate>Mon, 18 May 2009 12:21:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.powerobjects.com/2009/04/29/microsoft-dynamics-crm-or-sharepoint/#comment-1051</guid>
		<description>The correct answer is it depends. It depends on a number of factors, like the business objectives of the solution, licensing, infrastructure available, capability to develop and maintain and alignment of the solution with the technology that has the features that compliment it or provided out of box. Long and short of it, use both. 

Howerver this does raise a good question to debate. It’s too easy or high level to say SharePoint is great at unstructured data but not great at structured data. Talking about data at all in relation to SharePoint shows here the easy misconception. 

SharePoint is not only about data and therefore not designed to be good at structure or unstructured data. SharePoint is a platform that can be used to bring together people, process and information. Information in a variety of formats (html, word, powerpoint, excel, pdf), structures (unstructured, semi structured, structured) and locations (other LOB systems). People from a variety of origins and processes that fit for purpose. Plus it also has pretty handy WCM and Search capabilities. 

My suggestion is to chose the right horse for the right course. For some things it will be CRM, others SharePoint and for many more both and a whole lot more goodness.</description>
		<content:encoded><![CDATA[<p>The correct answer is it depends. It depends on a number of factors, like the business objectives of the solution, licensing, infrastructure available, capability to develop and maintain and alignment of the solution with the technology that has the features that compliment it or provided out of box. Long and short of it, use both. </p>
<p>Howerver this does raise a good question to debate. It’s too easy or high level to say SharePoint is great at unstructured data but not great at structured data. Talking about data at all in relation to SharePoint shows here the easy misconception. </p>
<p>SharePoint is not only about data and therefore not designed to be good at structure or unstructured data. SharePoint is a platform that can be used to bring together people, process and information. Information in a variety of formats (html, word, powerpoint, excel, pdf), structures (unstructured, semi structured, structured) and locations (other LOB systems). People from a variety of origins and processes that fit for purpose. Plus it also has pretty handy WCM and Search capabilities. </p>
<p>My suggestion is to chose the right horse for the right course. For some things it will be CRM, others SharePoint and for many more both and a whole lot more goodness.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Jones</title>
		<link>http://www.powerobjects.com/blog/2009/04/29/microsoft-dynamics-crm-or-sharepoint/comment-page-1/#comment-1047</link>
		<dc:creator>Dean Jones</dc:creator>
		<pubDate>Wed, 13 May 2009 18:40:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.powerobjects.com/2009/04/29/microsoft-dynamics-crm-or-sharepoint/#comment-1047</guid>
		<description>I agree but please post some examples where you use both. It&#039;s common on project to use SharePoint to manage documents in CRM solutions. How do you leverage both? 

Also it&#039;s important to know how a person works. When you come into the office what do you do? Login to e-mail? Login to CRM? Login to SharePoint? Most likely you don&#039;t do all three. The goal is to create a work space to make your office the most productive. Surf information where a user works.</description>
		<content:encoded><![CDATA[<p>I agree but please post some examples where you use both. It&#8217;s common on project to use SharePoint to manage documents in CRM solutions. How do you leverage both? </p>
<p>Also it&#8217;s important to know how a person works. When you come into the office what do you do? Login to e-mail? Login to CRM? Login to SharePoint? Most likely you don&#8217;t do all three. The goal is to create a work space to make your office the most productive. Surf information where a user works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Anderson</title>
		<link>http://www.powerobjects.com/blog/2009/04/29/microsoft-dynamics-crm-or-sharepoint/comment-page-1/#comment-1046</link>
		<dc:creator>Josh Anderson</dc:creator>
		<pubDate>Wed, 13 May 2009 18:34:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.powerobjects.com/2009/04/29/microsoft-dynamics-crm-or-sharepoint/#comment-1046</guid>
		<description>USE BOTH!!! They go hand in hand.</description>
		<content:encoded><![CDATA[<p>USE BOTH!!! They go hand in hand.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne Stanton</title>
		<link>http://www.powerobjects.com/blog/2009/04/29/microsoft-dynamics-crm-or-sharepoint/comment-page-1/#comment-1041</link>
		<dc:creator>Anne Stanton</dc:creator>
		<pubDate>Wed, 29 Apr 2009 17:16:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.powerobjects.com/2009/04/29/microsoft-dynamics-crm-or-sharepoint/#comment-1041</guid>
		<description>I like to talk about the difference between structured data (CRM) and unstructured data (SharePoint). SharePoint is great at unstructured data, but not great at structured data (not a lot of depth there) and vice versa for CRM.</description>
		<content:encoded><![CDATA[<p>I like to talk about the difference between structured data (CRM) and unstructured data (SharePoint). SharePoint is great at unstructured data, but not great at structured data (not a lot of depth there) and vice versa for CRM.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
