Dynamics CRM 2011 provides a very useful feature called charts. Charts can be designed within charts designer provided out of box and they can also be customized using charts XML. In this post we will look into various customization options available to design charts using XML.
Charts are used to display and portrait information in a meaningful way so that chart’s audience can quickly understand and analyse data trends. Some charts convey message more accurately than other. For example, a line chart conveys trending information better than a pie chart.
There are a handful of chart types available in charts designer such as:
- Column chart
- Bar chart
- Line chart
- Pie chart
- Funnel chart
- Multi-series chart
- Stacked charts
- Mixed chart
- Series chart
Dynamics CRM 2011 uses Microsoft Chart Controls for Microsoft .NET Framework 3.5. This framework is rich in functionality and provides more chart types. Following chart types can be consumed within Dynamics CRM 2011.
Let’s dig deep into Chart XML and Customize few of them to unleash their potential.
Microsoft Dynamics CRM 2011 is an innovative product with limitless possibilities to extend and customize according to various industry requirements. In last few years, Microsoft has improved CRM product but there are still some features missing specially in the area of mail merge. These gaps have been beautifully covered by many ISV’s by developing innovative add ons to support enterprise CRM deployments.
Today i will discuss selection of a mail merge addon for Microsoft Dynamics CRM 2011. CRM 2011 provides comprehensive mail merge functionality but still some advanced features as below are missing from this version.
- Ability to display 1-M records
- Ability to display multi hop away entities records
- Ability to convert documents in PDF
- Ability to perform logical / conditional formatting
- Ability to display Query based records
- Import Export Templates
- Security Configuration for Templates
- Auto Merge
There are two major ISV’s providding mail merge addons.
Here is a feature comparison for both ISV’s:
Ability to display 1-M records:
Both addons are very smart at handling 1: M relationships. Task Pane provides 360 degree view of all entities and their relationships as shown below:
In your templates, you will be able to create a 1: M (one to many) relationship in few clicks as shown below:
Ability to display multi hop away entities records
You can build complex relationship using FetchXML tool. Link entity section will provide you a way to attach entities in a relationship. This tool generated FetchXML as per you entity selection and you have an option to use your own FetchXML and build relationships on multi hop away entities as shown below.
Ability to convert documents in PDF
Both addons can convert generated document to PDF as shown below. Moreover, you can create an activity and attach generated document to it.
Ability to perform logical / conditional formatting
Both addons provides limited conditional formatting capabilities.
Ability to display Query based records
FetchXML is standard way to query Microsoft Dynamics CRM 2011 platform. Using FetchXML tool you can build any FetchXML query insert resultant fields to template as shown earlier. Both addons provides FETCHXML support,
Export/Import Mail Merge Templates
Both addons provide template import/export feature. Import tool provides possibility to deploy existing templates to a different organization.
Security Configuration for Mail Merge Templates
Both addons expose Template as a CRM record. In this way, user can benefit from CRM integrated security model to build various permissions on template depending on user security roles.
Auto merge feature is not included in DocumentCorePack addon. A separate addon is available by MSCRMADDONs for generation of documents automatically from processes.
Microsoft Dynamics CRM 2011 comes with a brand new concept of solutions. Solutions are how customizers and developers author, package, and maintain units of software that extend Microsoft Dynamics CRM 2011. In this post I will be focusing on development of enterprise CRM implementations and utilization of solutions.
In enterprise CRM implementations, many processes/iterations are running in parallel which result in many product releases in parallel. So development, testing and rollout of all releases in parallel with no interference with work in progress are massive challenges.
For example, your CRM implementation is comprised of N release as shown below and you want to utilize Microsoft Dynamics CRM 2011 solution concept to fulfil following goals:
- Development of releases in parallel
- Multiple teams working on multiple releases
- Testing of releases in parallel to development
- Release based rollout to production
- Install or uninstall releases from test or production
- Post production support (Patch/hotfix)
I am expecting that you are familiar with managed/unmanaged solution concepts. So in order to implement above scenario, you need to design your organization and solution structure for CRM 2011 accordingly as given below:
- Create a base organization and a base unmanaged solution in it
- This solution will carry generic customization i.e. account and contact entity customization
- Any generic plugins i.e. creation of counter/auto numbers on custom entities
- Configuration entities and plugins
- Add common security roles
- Create another organization for each release with one unmanaged solution per release
- Install base solution as managed in this org i.e. very similar to solution library concept.
- Add all release 1 specific components to release 1 unmanaged solution
Similarly, for all other release, use rest of all released as managed solution (reference).
Now, if something is changed in release 1 or base solution, you can use managed solution update feature. Just export new version of base/release 1 solution as managed and install it to release 2 organization by using overwrite or merge option.
Now let’s open the file in Text Editor available in web resource to add a function to show/hide a section/tab on form.
Microsoft Dynamics CRM 2011 provides new xrmPage model to access UI and data at client side. Here is a snapshot of the hierarchy.
Now let’s add library from solution library.
You can see that Details tab is now hidden and alert.
Microsoft CRM 4 lacks call scripting features and customer especially call center customer will have to buy 3rd party add-ons like TK Dialogues, custom ASPX pages etc. to fulfill this requirement.
However, Microsoft CRM 2011 provides call scripting out of the box using processes. Processes are now used in place of workflows. Microsoft has categorized processes in Workflows and Dialogs. Workflows are same old workflows but dialogs can be utilized in various ways i.e. Call Scripting, Approval Processes, User Feedback Process and many more as CRM 2011 gets introduced in various industry sectors.
In this post, we will discuss processes from two perspectives. One is related to designing a process and other is execution of processes. Processes are located in Settings -> Process Center in navigation pane as shown below:
Microsoft CRM 2011 provides a designer tool for designing processes and this designer tool is very much similar to workflow designer but much more capabilities as compared to workflow designer. Now you have the options to prompt and get user input into process.
For the sake of clarification, lets design a script for call center representative to ask first name and last name of customer whenever takes a call from customer.
This script will be designed to execute on phone call activity as shown in the category attribute.
Now we will add a page and then add two prompt and response steps for first name and last name and one prompt and response step for email.
We have almost designed are very simple Call script that will ask standardize our response when a call is received from customer. It will first ask for first name & last name. Then will ask for customer email address. Here we can specify as many steps as required to implement you call scripting needs and you can utilize the values gathered through this script to send emails. Create records as cases, contacts, activities, service activities etc.
Let’s Activate [published/unpublished is renamed as activated/deactivated] this process and Execute from Phone call activity. You can see from below screen that there are no more clicks involved to create a phone call activity. It’s pretty quick and easy. Thanks Microsoft for this consideration.
Now let’s execute the Call Scripting from phone call start Dialog as shown below:
Select the specific Dialog and click OK.
Click Finish at end of the process to and an email will be created.
and sent to customer upon completion of the process.
Please comment or send your feedback and keep exploring Microsoft CRM 2011.
Microsoft CRM can store files as annotation but is not a document management system at all. There are many ways to integrate CRM with Document Management Systems. My approach in this article is pretty much utilization of CRM as xRM. So this xRM based solution is built on top of powerful Dynamics CRM platform.
The idea behind this post is a cost effective way to create, persist, and distribute documents. Since document size can increase to GB’s so attaching documents as annotation is not a good idea and can clearly increase the size of database in days and degrade the system performance.
I am using FTP and FTPS protocol to manage documents. At CRM side i have created an entity representing document as a record and then associated this entity where ever required. So here is my entity.
I have document category and sub category (dependent picklist) to categorize and classify my document on FTP Server. I have a due date to trigger my document escalation/follow-up workflows. I have a status reason associated to a document (Draft/Approved/Pending/Rejected/On Hold/Reviewed). I have Upload and Download Button to save and retrieve document from FTP server. In the references section, I have the meta data attached to the document entity. The metadata could be a relationship to case/contact/account or any other custom entity. So in Case entity my document will appear as shown below:
I can instantly view the file without downloading it on local disk by just pressing download button and click open.
So now I can instantly Approve/Reject/On Hold/ Review in CRM by using ISV buttons depending on current user privileges.
I have a full log of actions on my document available with status, user performing action and dates.
I have a comprehensive log of correspondence on this document available as shown below:
I have configurable alerts regarding Pending document/document on hold or documents to be reviewed. They are available to me on daily/weekly/fortnightly/monthly etc. bases and they are right in my outlook with links to my document in CRM.
Also I can utilize these documents online in my customer portals (eService). My documents can be accessed online by using FTP/FTPs and utilized in various ways as below:
Online Product Catalogues
Online Product Notices
Microsoft CRM can store files as annotation but is not a document management system at all. There are many ways to integrate CRM with Document Management Systems. If you are looking for search within document, version control, and publishing workflow then this post is not for you.
The idea behind this post is to utilize CRM structural relationship model and build a Document Store to process documents and also a cost effective way create, persist, and distribute document. Since document size can increase to GB’s so attaching documents as annotation is not a good idea and can clearly increase the size of database in days.
I am using FTP and FTPS protocol to manage documents. At CRM side i have created an entity representing document as a record and then associated this entity where ever required. So here is my entity.\
I have document category and sub category (dependent picklist) to categorize and classify my document on FTP Server. I have Upload and Download Button to save and retrieve document from FTP server. In the references section, I have the meta data attached to the document entity. The metadata could be a relationship to case/contact/account or any other custom entity. So in Case entity my document will appear as shown below:
So now I can apply approval workflows in CRM whenever a new document is created.
Also I can utilize these documents online in my customer portals (eService). My documents can be accessed online by using FTP and utilized in various ways as shown below: