Quantcast
Channel: Microsoft Dynamics CRM
Viewing all articles
Browse latest Browse all 123975

Blog Post: Community Resources CRM Field Guide Chapter 25

$
0
0

It is week 25 in the review of the CRM Field Guide chapters from the book – The CRM Field Guide – How to CRM Like an MVP with Microsoft Dynamics CRM. This week it is the 28 page Community Resources chapter. This week completes the reviews of all 25 chapters of the book that I have blogged about over the last 6+ months. It has been a great learning experience for me personally. Even though I have been working with CRM since v1.2 in 2003, there isn’t a chapter in the book that I didn’t learn a new tip, trick, or best practice from my fellow CRM MVPs.

However,  there will be one more blog posting. I am working on a CRM Field Guide Learning Curriculum that will identify the first 10 chapters a person should read depending on their persona:

  1. CRM Admin
  2. Power User
  3. Business Analyst
  4. IT Support
  5. Developer
  6. New User

 

The learning curriculum will be published in about 2 weeks.

It is fitting that we wrap up the book review with the last chapter on Community Resources.

The resources referenced in this chapter was assembled by asking MVPs to submit the links to the resources we use. So you get twitter handles, blog posting urls, CRM Team and Microsoft sponsored content links. Along information and resources directly integral to the product like the SDK is online.

At our company this is one of the first ‘tools’ we provide to our new members to our CRM team to get them ramped up quickly and listening to all the CRM chatter and insight.

Microsoft Dynamics Twitter Feed Samples

Microsoft Dynamics Twitter Feed Samples

Microsoft Dynamics CRM Blogs of Interest

Microsoft Dynamics CRM Blogs of Interest

The post Community Resources CRM Field Guide Chapter 25 appeared first on Innovating on CRM.


Viewing all articles
Browse latest Browse all 123975

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>