From the Microsoft Dynamics CRM Blogs: Cascading Entity Relationship; Salesforce Competitive Analysis; Disabling Fields; Missing Outlook Ribbon

Configuring Cascading Entity Relationship Behavior: Donna Edwards offers configuration tips on her MSCRM Dynamics Blog. She uses the Contact entity as an example to show how cascading behavior impacts CRM data.

She explains:

A common action that users might take on a Contact record is to reassign the record.  By default, that means that when a Contact record is reassigned to someone else (ownership change) other related record ownership will also be updated to the new Contact owner.  Ownership for related records like a Case, E-mail, Task, etc. will change to the new Contact owner for those records that are in an Active or Open status.  This can be confusing for the end user when viewing the records because it can appear that someone different from the original owner (created by) created the record.  We can modify this behavior to alleviate the confusion and ensure that the related record maintains its original owner.

Edwards provides screenshots showing the steps to configure the cascading behavior of the Contact entity's relationship with the e-mail entity.

Dynamics CRM vs. Salesforce - An update: How do these major CRM products stack up against each other? Leon Tribe analyzes the numbers once again and discusses it on his blog, Leon's CRM Musings. He takes a look at customer size, market maturity, and whether Dynamics CRM is catching up to Salesforce, and he offers financial insights.

The data he includes in his graphs or tables came from Microsoft ...