Today I attended the CRM 4.0 partner readiness tour and I took the opportunity to ask the technical specialist from Microsoft headquaters a lot of questions. In regard to my entry yesterday concerning licensing, we had an interesting discussion on how it can be managed and how it is handled in CRM 4.0.
In general the same licensing limitations apply as I described in my previous post. The new “light”-userlicense I described bellow will be a read-only user license with a reduced price. The external connector will also be available at a substanially lower cost.
However, we found some technical workarounds that the Microsoft representative actually said were ok but I havn’t asked a Microsoft sales rep and I don’t know if I should…
If you want to create dynamic reports based on CRM data, what you must do is to replicate all the data that you want to base your reports on to your own database. Then create all the reports based on this database, which can be called datawarehouse or something similar.
The same “intermediary” database can also be used when you have, for instance, an internal support page where you can submit your support issue, which is then added to the CRM as a Service case. Let the application write to a database and then create an service that periodically (like every minute or so) reads the new data, and writes to the CRM webservice. There are other similar ways of doing this (like sending emails from the form to a support que) and I think you get the general idea.
The legal workaround using a subsidary company with an external connector license is also valid, but will require you to buy the external connector which has a non trivial price.
I feel this is very strange, that you using a technical solution can bypass some licensing rules that actually should be changed.
CRM and SharePoint Consultant
During Convergence 2007 in Copenhagen, it got into a discussion with some Microsoft empolyees concerning the licensing issues when creating applications that directly or indirectly access CRM-based data.
According to what I have heard, it boils down to the fact that a user license is required for all users who interact with the data in any way. This means that no user license is required for a static report displayed in, for instance, SharePoint, but, as soon as there is any interactivity with the data, as for instance, drill down, a separate user license is needed.
So, if you want to display data in SharePoint that comes in whole, or part, from the CRM-database, make sure it is a static report, so that no special user license is required. Creating a report (with for instance SQL Reporting Services) that has drill-down, will require each user to have a user license.
This rises the question of what kind of licensing is needed to access OLAP cubes that are assembled from a data warehouse based on data from many different system, among these, Microsoft CRM. As far as I have understood a full user license is required for all users who can access the OLAP-cubes.
This issue will probably change in CRM 4.0 when there will be a new “light-user-license”. Exactly what this means is still unclear and I have heard no details from Microsoft.
When creating any outside interaction with CRM, like a web based tool for submitting service cases, the separate “External Connector” license is needed. This is independant of the magnitude of the application or number of external users (company employees cannot use the external connector). It is also independant of if each user actually uses a named user or some common system user. I am unsure of the exact price for the external connector, but I believe it is somewhere around $40 000.
So, what does this mean for CRM-developers? That we have to have some basic understanding of the licensing modell and what limitations there are to it, so that our customers don’t have to pay unnecessary license fees just because we thought that drill-down was a nifty feature in our report that is published on a SharePoint portal.
As many of you, I think these limitations are non benificial for Microsoft since they greatly restrict the possibilities of creating nice Mash-up applications and portals, something Microsoft technology is very good at and something I would view as a great advantage in comparison to Microsofts competitors.
I would also like to point out that I might be wrong in understanding some of these details, and I would be greatful if you could leave a comment if you know or think that I might have understood something wrong.
CRM and SharePoint Consultant
Humandata AB / Soon Logica CMG/WM-Data
Now Convergence is over and I feel stuffed with info and experiences. There is so much I would like to write about and so little time. I will try to spread it out a bit.
During one of the sessions Clint Warriner, an Escalation Engineer (he writes hotfixes) held a very interesting chalk-&-talk about CRM system maintanance and performance best practices.
It was crammed with goodies, and I will write more about it later, but one interesting thing he talked about was the possible delay in loading forms. He said this, most often, depends on the SQL server. When loading forms the list of which reports are relevant and so on, are also loaded from the Reporting server. This can, in some cases, take some time, and in some bad cases, really afect the load time of forms.
They have created a hotfix for this, that can be requested from Microsoft support (no cost) if you give the referece: KB 941592. It simply caches the information on what reports exist so that the request to the SQL-server doesn’t have to be executed every time.
I will get back to the subject of performance tuning later.
CRM and SharePoint Consultant
I am writing this posting from my hotell room in Copenhagen on the end of the second of the three days of the Convergence event.
As you can expect, a lot of focus is on the new CRM 4.0 and all the brilliant new features of it. The other Dynamics products, mainly NAV and AX are also getting some of their well deserved air-time, but for me, it is all CRM! 🙂
So, anything interesting? Yes, a lot. I will be digging deeper into some of the topics later but would just like to write a little bit about everything I have seen and thought about thus far.
CRM 4.0 – What’s new?
Well, a lot.
Multi, multi, multi!
Most of the focus is of course on Multilanguage, multicurrency and multitenancy. I personally feel that from the perspective of where I usually work, the two foremost “multis” are the most interesting. Multitennancy is maybe most interesting from a large enterprise view or hosting environment view
Microsoft Dynamics CRM 4.0 (as it formally is called, I will just call it CRM) has the ability to work as an Internet facing application, which CRM 3.0 wasn’t (appart from CRM 3.0 SPE). This is really good news since it is really to be expected of the product. I havn’t been able to get any info yet on how this works with MS ISA running reverse proxy (like you do in SharePoint) but I would imagine that it works (it didn’t work very well in CRM 3.0).
Better Outlook client
The outlook client has gotten a major workover, and is now more stable and has a better interface. Some features to mention in that it will show a progressbar when loading and won’t block the usage of Outlook during this time. It also allows for syncronization of other activity entities that just email, contacts, calendar and todo’s, like for instance phonecalls and faxes. I havn’t seen this in action yet.
The email subject tokens are gone! Exaclty how it is handled in CRM 4.0, is still unclear for me, but it is probably handled in the mail header somehow. Emails can also be converted to leads and cases directly.
Autocomplete in lookup fields
One very timesaving feature is that the well know autocomplete/intellisense function has been enabled on all lookupfields, vastly reducing the clickyness of CRM. Good job!
A lot can be written about this, but in general it uses one server installation language (default language) and then MUI-packs can be installed on either the server or the client to be able to run CRM in another language. Multi language is supported for picklists, sitemap, isv.config and more but not for CRM content. This might not seem like a problem but it is, since for instance products and subjects are CRM Content. If you are looking into using this feature you had better look into it thoroghly.
The tenant is set up with one Base currency that will be used as such and will for instance be the currency used in reports. Pricelists are in several currencies and exchangerates can be set using the webservice.
The mail merge has been improved a lot. Web client based mail merge has been activated (is only available using the Outlook client in CRM 3.0). Language specific mail merge templates can be created. Mail Merge has been enabled for custom entities.
CRM – Excel
Excel connections can be either iqv (like CRM 3.0) or ODBC. Refreshing of data is supported and a very very powerful feature of enabling updating back to CRM is also supported including creating new objects. This is very powerful since it can be used to clean data and do imports in a simple manner.
Office Communication integration
Office Communicatior has been integrated and you will get presence info in CRM. Very useful!
A new feature called the resource center has been added that allows role based info to be shown to the client. I don’t know the specifics of what can and cannot be done yet.
Two new licensing methods will be supported. Per device licensing and a “simple” user license, to be used for users who might only need to view CRM data shown in SharePoint in an agregated view. The details of the later licensing method, and what it will be called, is still very unclear. There will be no price difference between the per user and per device license. I will get back to you when I know more about this.
Diagnostics and troubleshooting
There are some additional tools to facilitate diagnostics and troubleshooting. Tools mentioned are Office Client Diagnostics and the possibility to switch on tracing in CRM (very performance demanding). There is also some sort of “self-healing” going on in the client. Exacly what it does is still unclear.
This has been discussed before in this and other blogs. In short, all that you wanted from CRM 3.0 is there in CRM 4.0 – many – many, 1-1, self referential, system – system. I havn’t heard of any limitations to this yet, but I am sure there are some (like maybe relationsships to “order product” or “quote product”.
The workflow handling is totally new and has been moved to Windows Workflow Foundation. (.NET 3.0). This is great news since this allows for REALLY advanced workflows.
In short, you don’t have to go to the server to create simpler workflows, they can be created from the web gui. A lot more creation options are supported, publishing of workflows is supported, there is a nice wizard, you can create workflow templates.
Also, the “sales process” has been removed and “stages” has been added to normal workflows, and can hence be used in all workflows, for all entities.
Workflows can now traverse relationships, the date-time handling is a lot better and the branching options has been improved a lot with support of “else” and “wait” statements. Dynamic data in forms is also supported using Workflow.
This is also an area that has been re-written a lot. Reports are now run directly on the CRM server, which gets rid of all Kerberos delegation issues. There is a nice end-user report wizard that is about as hard as creating an advanced find saved view. Reports are language specific (if you want them to be). There is support for scheduling directly from CRM. There is support for offline reports.
There is now a nice wizard for importing data and it is possible to save and export the datamapping. It supports all entities. It supports backing out of an import, even several weeks later.
An advanced and customizable dupicate detection exists that allows for cleaner data.
As promised, all supported customizations are supported for uppgrading, including callouts. There is a nice wizard that checks for possible problems before. Even though there are nice promises, I would really like to see this work before I believe it! It is almost to good to be true!
The exporting of security roles is now supported. When exporting all customizations, even all dlls that have been added as plug-ins are included. This will enable the movement of an entire solution from one server to another. (Ex. test to production).
Scale out possibilities
CRM has been split up into several services that can be distributed to several machines, so workflow, for instance can be moved from the front-end web servers to dedicated servers allowing for better scale-out options and greater performance.
The metadata webservice now enables writing, so new attributes, entites etc. can now be created programatically!
Create users in bulk
This has also been discussed in other blogs, but in short, it allows for the bulk creation of many users at once.
Well, that was a short overview of some of the new features in CRM 4.0 and I have hardly mentioned plug-ins.
I have attended lots of different sessions and will write a lot about it soon! As for now, the dinner table is calling (as is my belly!).
Over and out!
CRM and SharePoint Consultant
Humandata AB (soon WM-Data)
Integrating with map services like Microsoft Virtual Earth, Google Maps can bring your CRM or SharePoint application great increases in features at a relativly low cost. Microsoft uses Microsoft Virtual Earth internally and the Microsoft SharePoint Products and Technologies Team Blog has written an interesting posting about this which includes a reference to a codeplex project including all code for the internal project.
I havn’t checked it out, and it is used for SharePoint in the example but I believe that a lot of the code probably can be used to develop a Virtual Earth driven map service in Microsoft CRM.
So, without further ado, please read the posting and check out the codeplex project if you are interested!
CRM and SharePoint Consultant