From the CRM Blogs: “Append” vs. “Append To” Security Permissions; Easy Emailing from a CRM Contact Record; Entity Display Areas and the CRM SiteMap

 What's the Difference Between "Append" and "Append To" Security Permissions?  CustomerEffective's Joel Lindstrom answers the question in a guest post on the Microsoft Dynamics CRM Team Blog: "I find this confusion comes from the similar sounding names of these permissions, and also because configuration of relationship security requires permissions to be applied to two separate entities-both sides of the relationship. Let's take the example of Accounts and Opportunities.  In this relationship, "Accounts" is the parent and "Opportunities" is the child...

There are multiple Opportunities per Account.  Say a user needs to be able to relate Opportunities to Accounts, either through the Potential Customer lookup field on the Opportunity, or through the "Opportunities" navigation bar area on an account... In this example, a user must have "Append" permissions on Opportunities (child) and "Append To" permissions on Accounts (parent).  I think of it this way-I'm APPENDING the opportunity, and I'm APPENDING it TO the account..."

Create an Easy Emailing Button in a CRM Contact Record: From the Dynamics Method blog: "Has anyone else wanted to be able to click on the email address on a form in CRM and have it email that person/record? Or at least bring up an email message form that can be filled out and sent? Yes, on the Contact form there is the "Send Email" button, but that sends a CRM email and personally, I'm not a huge fan... So, the other day I came up with ...