<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Renaming or Repurposing Microsoft CRM System Entities</title>
	<atom:link href="http://thecrmarchitect.com/2009/09/23/renaming-or-repurposing-microsoft-crm-system-entities/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecrmarchitect.com/2009/09/23/renaming-or-repurposing-microsoft-crm-system-entities/</link>
	<description>The CRM ISV Experience From the Trenches</description>
	<lastBuildDate>Tue, 10 May 2011 13:05:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Dustin Miller</title>
		<link>http://thecrmarchitect.com/2009/09/23/renaming-or-repurposing-microsoft-crm-system-entities/#comment-104</link>
		<dc:creator><![CDATA[Dustin Miller]]></dc:creator>
		<pubDate>Wed, 23 Sep 2009 13:51:49 +0000</pubDate>
		<guid isPermaLink="false">http://thecrmarchitect.com/?p=231#comment-104</guid>
		<description><![CDATA[I think you have it right on here.  So many times in demos and training I have to explain that contacts and accounts are really the people and companies we work with.  In that case I am thinking of them with a different name simply to help a user with terminology.  If their environment thinks of contacts as people then by all means renaming the entity is an option if they can accept the cost compared to training people in the difference of the terminology.]]></description>
		<content:encoded><![CDATA[<p>I think you have it right on here.  So many times in demos and training I have to explain that contacts and accounts are really the people and companies we work with.  In that case I am thinking of them with a different name simply to help a user with terminology.  If their environment thinks of contacts as people then by all means renaming the entity is an option if they can accept the cost compared to training people in the difference of the terminology.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

