Microsoft Dynamics® CRM Training
A BluePrint for Dynamics CRM
An error occurred while loading the video. Please try again.
If we are honest with ourselves, this application, while tremendously robust, must nevertheless be configured to meet your needs. To ignore that fact, often results in failure. If we look inside of this application, we see modules, such as Sales, Service and Marketing. When we look inside those modules, we see entities - many of them, such as Accounts, Contacts, Leads, Opportunities, Activities. All of these modules and entities represent a LOT of functionality. All very powerful ways to track just about anything you need to track. In our experience, there are a couple of very important questions we get:
- Is there any way to simplify this?
- Often in the same breath ... "there are a couple of things missing. Can we create them?"
It's sounds a bit contradictory, but it's not. In the last six months, for instance, we have been asked to configure "Projects", "Properties", "Events", and "Financial Info" in various instances of CRM. This is what we call the Configuration of Microsoft Dynamics CRM. And it should be approached like any construction project. When you have a construction project like this, the first question that comes up is "Do I want to do this myself? Do I need some help?" These questions makes sense. There are avenues in both directions. For instance, for the folks who want to do it themselves, there is the Success Portal. Over three hundred videos in that resource, many of them how-to for customizations.
Even if that vast library of knowledge is available, we recommend a few things that you won't find in such as resource, such as:
Business Analysis Specific to Your Needs
Process Engineering for YOUR Processes
Best Practices for YOUR Application
What is required is a "BluePrint" for Dynamics CRM. This
consists of a document that lists the customizations , and also
provides a literal architectural blueprint that shows the entities
and the relationships between them. This is also referred to
as an Entity Relationship Diagram. It's a technical
document, but this kind of artifact is quite useful for whomever
configures your CRM. The material that precedes this is also
invaluable because it provides a road map of what function each
entity is intended to serve.