Tag: Leo

Update Rollups, Service Packs, Major Releases: Understanding Dynamics CRM Versioning
When it comes to commercial software, there’s often times a difference between what the engineering department calls their product versions and how the marketing department decides to label the product for the end customers. For example, after Windows 3.1 the commercial name of the product changed to “Windows XP” while the underlying version number progressed to 4.00. After various changes in both product and naming strategy of the OS, we’re now using a product called “Windows 8.1” when its actual technical version number is 6.3…

Just like with Windows, Dynamics CRM also has version numbers that are different from the names you’ll see in marketing materials and end user documentation. These numbers are relevant to anyone who needs to either maintain and administer a Dynamics CRM environment or customize and develop solutions for the product, since you need to be aware of the changes introduced by various updates to Dynamics CRM.

Before CRM 2013 there wasn’t a convenient way through which you could have determined the installed updates by just looking at the version number, since each Update Rollup just had a seemingly random four digit build number assigned to it. Luckily the latest releases have made the version numbers much more user friendly, by starting to follow the standard “major.minor.update.build” pattern. There’s still a few CRM specific things you need to be aware of, especially with the very latest releases, which is why I thought now’s a good time to draw some attention to the topic.

Starting with CRM 2013, the version numbering scheme follows a pattern like this (notice the bold numbers):
- Major Release
  - Name: Microsoft Dynamics CRM 2013
  - Version number: 6.0.0.xxxx
- Service Pack:
  - Name: Microsoft Dynamics CRM 2013 Service Pack 1
  - Version number: 6.1.0.xxxx
- Update Rollup:
  - Name: Microsoft Dynamics CRM 2013 Update Rollup 1
  - Version number: 6.0.1.xxxx
The build numbers are of course not “xxxx” in reality but I left them out since they’re not something you should actively need to remember. Just bookmark this page and reference it whenever you need to know the detailed number of a particular release: Microsoft Dynamics CRM 2013 and 2011 Update Rollups and Service Packs: Release Dates, Build Numbers, and Collateral.

I’ll go through these levels in a reversed order, since I think that makes up for a more exciting story line here. Also, I think it’s more likely to resemble the real life process via which you’ll encounter each of these versions of Microsoft Dynamics CRM after your initial deployment. You’ll certainly need to be aware of the different versions even prior to setting up your very first demo/test/development environment, but keeping up with the Dynamics CRM releases is a job that never ends!

Update Rollups

These are collections of hotfixes to existing product functionality. When you open a support ticket with Microsoft for an issue you’ve encountered with the software, sometimes you might receive an individual hotfix package from them that fixes your specific issue (and nothing else). Normally you wouldn’t need to install each and every hotfix separately, however, as most of these fixes will eventually be released in an Update Rollup package. You’ll see a list of “issues that are resolved” in the Microsoft Knowledge Base article of each Update Rollup, which is normally your best indication of whether the software bug you’ve encountered has been squashed.

<rant>Since the official name of these releases is “Update Rollup”, the official acronym for them would logically be “UR”. However, some people seem to happily forget about the first word and instead call them “RU”, presumably as a shorthand from “RollUp”. Fine, call them whatever you want, even give each of the releases your very own pet names if you wish, but you’ll never, ever see me use anything but “UR” on my blog.</rant>

At the time of writing, the latest released version for CRM 2013 is Update Rollup 3, version number 6.0.3.0106. It was released on July 15th and contains over 200 hotfixes as listed on the KB article. Normally there would be a UR3 package released for all the server and client components, but this time there’s no Outlook version available, since apparently none of the hotfixes required the client bits to be updated. Update Rollups are usually cumulative, so CRM 2013 UR3 also contains the fixes from UR1 and UR2.

If you don’t manually download and install the UR’s, they will also be distributed via Windows Update later on once Microsoft makes them available via this channel. Since you should always test the effects of each UR prior to production deployment, it’s usually never a good idea to just let things run on autopilot. For example, letting your Outlook clients get the UR’s via the Windows Update schedule without keeping your server components up to date will soon land you in unsupported territory.

Service Packs

During it’s first 11 years of existence, there weren’t any official Service Packs released for Dynamics CRM, unlike many other Microsoft products. This changed a couple of months ago when CRM 2013 Service Pack 1 was released on May 28th. Even though MS is mostly referring to it by the name Spring ’14 release in their marketing messages, based on the naming policy of CRM Online, the SP1 version is essentially Spring ’14 for on-premises customers and the Outlook client components (even for CRM Online customers).

While the CRM 2013 SP1 KB article looks like any UR article we’ve come to know, with a list of resolved issues, this isn’t just a collection of hotfixes. Service Packs are the delivery mechanism for new product features as well as changes to existing functionality of the product. An example of this would be the case creation and routing features introduced in SP1. For a more complete list of SP1 contents, refer to the “What’s New” page on CRM Customer Center. Note that in order to access some of the new features, you’ll not only need to install the SP1 bits onto the server but also go to the CRM organization’s settings menu and apply “Install Product Updates” from there.

Service Packs are cumulative in the sense that they contain the previously released Update Rollup hotfixes. So, while CRM 2013 UR1 and UR2 were released prior to SP1, you don’t need to install them separately when setting up a new Dynamics CRM 2013 environment. Just grab the Service Pack and you’re all patched up to that point.

Update Rollups for Service Packs

Now this is where it really gets interesting. Remember that latest CRM 2013 Update Rollup 3 I linked to a few paragraphs earlier? Based on our discussion so far, would you assume it to contain all the fixes, updates and new features released for CRM 2013 so far? I see quite a number of nodding heads out there and I’m not at all surprised if your initial assumption would be “of course”. The correct answer, however, is “no”. Due to the counter-intuitive nature of this situation for any Dynamics CRM veterans, an explanation is surely in order here. (more…)
July 17, 2014
Configuration Migration Tool: Working Smarter with Metadata Entities

If you mostly work with configuring the Microsoft Dynamics CRM solutions via the customization UI with its graphical point & click tools instead of writing custom code in Visual Studio, you may not keep such a close eye on the changes introduced in the CRM SDK. After all, the term SDK stands for “software development kit” and you may not consider yourself as the target audience if you don’t actually develop any new software that would interface with Dynamics CRM.

The What’s New page in the CRM SDK documentation is a place that would be very useful for also non-developers to have a look at whenever updates to the product are released. Apart from the end user guidance material published on CRM Customer Center, the SDK is pretty much the official place where changes to the platform functionality are introduced. With the latest CRM 2013 Service Pack 1 release (a.k.a Leo) now available, there’s a long list of new and improved features to review. One new addition that didn’t receive a mention on that page, though, is the Configuration Migration Tool, which is a very handy tool if you need to transfer metadata entities across different CRM organizations.

What Are “Metadata Entities”?

In theory the CRM solution files should contain all of the configuration data about your CRM organization. This is what is often referred to as metadata, which could be described as “data about data” in short. As an example, the list of possible values for the Relationship Type attribute on your account record would be considered metadata, whereas the actual account records referring to one of these values would be “real” data stored in the business entities. To illustrate the difference, a blank CRM organization containing only your customizations would not contain any records for the business entities (accounts, contacts, opportunities), but it would contain all of the records in the metadata entities that would be necessary for executing the customized business processes, since otherwise the configuration of that environment would be incomplete.

In practice there are often valid reasons for why it makes more sense to store this type of metadata in a custom entity of its own, instead of using option sets. This provides a whole different level of flexibility in terms of what type of metadata and how much information you can store. Maintaining the list of values can be done without the need to update the customizations. Filtering available records to the end user can be done via standard security roles and BU’s. Building dependent lists on the form can be achieved via the filtered lookups feature. You can leverage the new Quick View Forms to show data from related parental records. And so on.

One problem with using these type of metadata entities is that the data cannot be packaged into a CRM solution file. While you can easily export any changes to the standard customization components and move them to a different CRM organization, getting the metadata entity records from one org to another requires a bit more effort. As a result, keeping the different development, test and production environments in sync requires specific attention to be paid on these metadata during the release process.

Introducing the Configuration Migration Tool

The CRM 2013 Service Pack 1 release includes the new Unified Service Desk (USD) application that relies heavily on storing its configuration data into these metadata entities. In order to support the systematic deployment of USD solutions configured for the customer’s environment, Microsoft has introduced new tools in the version 6.1 (a.k.a. CRM 2013 SP1) SDK. These are the Configuration Migration Tool and the Package Deployer tool. While the latter one is surely useful in deploying larger ISV solutions, I believe it’s the Configuration Migration Tool that can benefit a far wider audience. Also, since you don’t need to run Visual Studio to work with the tool, I’m personally more comfortable discussing its features in my blog as a non-developer who generally steers clear from anything that isn’t close to point & click.

In short, what the Configuration Migration Tool (from here on referred to as “CMT”) allows you to do is 1) choose the entities that you want to migrate data from, 2) export all the records from those entities as a .zip file and 3) import it into a different CRM organization. There’s a great illustration available in the SDK article describing CMT, presented below:

“Awesome, now we have a built-in tool for CRM data migrations!” Well, actually, no. While CMT can move a set of records from several entities in one package and maintain their relationships, it has not been designed for the purpose of business data migration. For example, you cannot filter out any of the records to be transferred from the source organization, nor are there any guarantees for the tool’s performance when moving very large sets of data. Here’s what the Dynamics CRM product team has to say about the tool:

Check out this CMT feature overview video on YouTube for more information on the above points.

Moving Configuration Data with CMT

Let’s see how the tool works in practice. To test the features, I created two custom entities for storing my configuration data: “Category” and “Subcategory”. A category can have many subcategories (1:N relationship), but in order to make the experiment more interesting, I also added a lookup on the category form that allows selecting the default subcategory to be used. So, we have both a 1:N and N:1 relationship between our entities, as shown on the Category form below. For the purpose of testing I added category A with subcategories 1*, 2, 3 and 4, then category B with subcategories 1 and 2*, with the asterisk determining the chosen default subcategory (notice the duplicate names in the subcategory data, we’ll get to that later on).

After launching CMT, choosing to define the schema (step 1) and entering the connection information to log into my own development CRM 2013 server via IFD (hint: enter the server URL with the org name as “org.domain.com” and the user name as “user@domain.com, no other connection option worked for me), we’re presented with a screen for choosing the components to be included in the schema. We can pick from entities included in a specific solution. After selecting the entity, we can either choose which fields we want to transfer data from or just be lazy and add the whole entity into our schema definition. Save and Export will give us an XML file with the contents from the included entities, fields and relationships.

The next step is the data export. Here we’ll choose the schema XML we just created and a target file for the data export. Hitting the Export button will start the process, report the progress for each entity in the CMT app window and finally produce a .zip file containing the data for all the components defined in the schema file.

The last step is to connect to a different organization that already has the same schema. So, if you’ve not yet transferred your solution files into the target organization, now’s the time to do that, since CMT will not modify the organization schema, but rather just assume that it is identical to the source organization as far as the selected entities and fields go. (more…)

June 9, 2014
CRM 2013 SP1: Case Creation and Routing – The Details

In my previous post about the new functionality included in CRM 2013 SP1 / Spring ’14 release I laid out the big picture of how case creation and routing rules relate to cases and queues in Dynamics CRM. Now it’s time to take a more detailed look at how you would actually configure these rules to automate your case creation process. There are a few limitations that it’s good to be aware of before you jump into applying these new tools in your service management scenarios.

Case Creation Rules

As illustrated in the big picture of queue and case management in my previous article, Case Creation Rules are specific to a single queue. Also, you can only have one Case Creation Rule per queue – per channel. It is nevertheless a 1:N relationship between queues and rules, since a queue can have a Case Creation Rule both for email and social activities (the latter of which are not yet leveraged in this release). The Command Bar buttons on the updated queue form, labelled “Email To Case Settings” and “Social To Case Settings”, take you to the respective rule record.

The Case Creation Rule form allows you to configure predefined conditions for case creation. Emails from unknown senders can be filtered away from case creation. Also the existence of a valid entitlement for the sender (contact) or the senders company (parent account) can be used as a filter. Finally, email related to an already resolved case can be set to generate a new case record, with a configurable “quarantine” time period. So, if you resolve a case today and the customer replies “thanks for your help”, this probably shouldn’t generate a new case, but a reply sent after 3 days to the same email thread might warrant opening up a whole new case record.

That’s all the conditions you can apply for the automatic case creation. There’s an additional entity called Case Creation Rule Item that’s found in the “Specify Case Details” subgrid. What this feature allows you to do is specify a condition on the activity record (email or social activity) and set values for the newly created case’s fields. As an example, if the email subject contains word X, you could populate the case subject lookup field with value Y. So, you can’t use these Rule Items to determine whether a case will be created or not, but you can pass along some variables from the originating activity.

The entity fields you can access in the Conditions box are limited to those directly related to the email (or social) activity. There is however one welcome exception and that is the Senders Account. This means that when the email is coming from a known contact, there’s a way to reach into the fields of the account related to the contact (related to the activity), to check variables like relationship status, customer category or other important pieces of information in a B2B service scenario. (more…)

June 3, 2014
CRM 2013 SP1: Case Creation and Routing – The Big Picture

The latest Dynamics CRM Online Spring ’14 release is now rolling out to existing and new customers (starting from the US data centers) and the on-premises equivalent of CRM 2013 Service Pack 1 ~~will soon follow~~ is now available from MS Download Center (here’s the KB article for more details about SP1). The quickest way to check if your CRM Online organization is already updated to the latest release is on the About screen, accessible via the gear icon in the top right corner. If your version reads 6.1.0.575 (or 6.1.anything) then you’ve got the Spring ’14 release available and you can proceed to the Install Product Updates menu to enable the new features.

This release, previously known by the codename “Leo”, focuses on enhancing the service management capabilities of Dynamics CRM. There’s a great “What’s New” page on CRM Customer Center that provides a detailed listing of the new features launched now, including an eBook of the changes in service management. Instead of repeating all of this information, I’ll try and provide an overview of how the features align with one another and specifically how they could be applied in real world scenarios for managing incoming service cases from customers.

Enhancements in Case Creation and Queues

I guess we’ll still need to first list the new options we need to be aware of when configuring the service module in CRM 2013 SP1 to handle emails and cases via queues. First off, there is now support for server side synchronization of emails (and other activities) between CRM Online and Exchange Online, without having to use the old Email Router technology (no support for hybrid deployments, though). Then there’s a new feature called Case Creation Rule that allows you to automatically convert an email message or a social activity record placed in a queue into a new case record. Finally, we have Routing Rules that can be leveraged for moving items into queues.

The following is my own interpretation of how these three areas are aligned in CRM 2013 Spring ´14 Update / Service Pack 1. The picture illustrates how an email message from the customer would flow through the system automatically based on the configuration of the aforementioned features. It also includes a few bullet points about the supported actions for each component. (Feel free to click on the image to view a bigger version that won’t stress your eyes so much.)

When going through the Leo release features I found it a bit challenging to get a clear view of the logical order in which the different functional areas found under the new Service Management settings menu should be applied. Also the relationships between them and the restrictions imposed on the number of records was something I only learned through trial and error. Hopefully this illustration makes it easier to identify the roles of case creation rules and case routing rules in the new release.

Rules vs. Workflows & Plugins

Looking at the picture, someone who has previously configured Dynamics CRM to be used in an email, queue and case based support process will surely find many familiar actions from the list. At the end of the day, pretty much everything here has already been possible with previous CRM versions. With those you just needed to leverage the workflow engine in the CRM platform to configure the case creation and routing activities. So, what’s really new here and why has Microsoft built this into the latest product release?

Behind the scenes, what the case creation and routing rules do is they create the workflow processes for you. This can be seen from the release documentation where the administrator of those rules is reminded about the requirement to have sufficient security roles for performing the corresponding actions via workflows. So, taking a very simplistic view, you could think of these new features available in the Service Management as a dedicated UI for configuring common process automation actions for customer service scenarios.

There’s definitely value in having these new features available right inside the core product. In previous versions, it has been far from trivial to build the necessary functionality for frequently encountered requirements, such as “email to case”. Several ISV add-ons have been developed to deliver such functionality and system customizers have surely spent a ton of time pushing the CRM workflow editor to its limits in an effort to automate the common tasks that a service organization would need to perform when managing cases in Dynamics CRM. Now there’s a new standard way to implement these processes via a method that is fully supported by Microsoft, which in turn will lead to far more customers taking a serious look at these case management capabilities in their business application platform.

It’s important to keep in mind that these new features don’t replace any of the existing CRM platform functionality. They offer a default method to configure common features, but they will not cover every possible scenario that you’ll come across in real life implementation scenarios. That means you can still use workflows and plugins to extend the process automation for service case management. For example, while a case creation rule provides the possibility to set an auto response email to be sent to the customer upon case creation, there’s nothing stopping you from doing this via familiar workflow process if more complex business logic is needed than what the new Service Management UI in CRM makes available.

In the next blog post I will take a more detailed look at how the case creation and routing features can be leveraged in practice, so stay tuned!

May 24, 2014
What’s on the 2014 Roadmap for Microsoft Dynamics CRM?

The annual festivities of the Microsoft Dynamics Convergence event in the US have now been completed for the year 2014. This means that the outline for upcoming releases in this calendar year have also been presented to the 12K attendees in Atlanta as well as anyone watching the sessions via Virtual Convergence. The following roadmap slide shown at the event tells us the big picture: it’s going to be a busy year for Dynamics CRM!

OK, so if the first “swim lane” in the CRM Roadmap schedule is titled “CRM”, then what’s with all the other lanes then and how do these non-CRM items relate to the Dynamics CRM roadmap? Well, here’s the thing: this ain’t the CRM you used to know. It’s no longer that IIS application you used to install on your own little Windows server along with a SQL database and maybe a client component in Outlook. It’s now a suite of services that cover not just your internal processes and tools for your employees but also a wealth of external touch points where your customers will also encounter your CRM system, be it directly or indirectly. Oh, and naturally most of it lives in the cloud, because that’s also where your customers are.

Of course customer relationship management has never been about just that single CRM database where you keep your own contact records, but now it has become very obvious that also Microsoft’s offering in the field of CRM has grown way beyond that. Following on the footsteps of Oracle and Salesforce.com, the acquisition and integration of a growing number of tools to complement the traditional core Dynamics CRM platform means the future CRM product will be much more modular, as opposed to the earlier “one app & license for everybody” approach. Let’s go through each of these lanes in the CRM roadmap and look at what was announced for them at Convergence 2014, starting from the most familiar one: “CRM”.

CRM

After last fall’s release of the new Dynamics CRM 2013 major version (code name Orion), you might have been lead to believe that there wouldn’t be so much happening with the core platform this year, at least in the on-premises world. The earlier communication from Microsoft indicated that the plan was to introduce a new release for CRM Online twice a year and roll out an on-prem version once a year. The code names for these releases were also shared: Leo in Q2 2014 and Vega in Q4, one year after CRM 2013 RTM.

This is no longer true. But wait! It’s not an R8 style cancellation but rather a positive piece of news. The Q2 2014 release Leo will be for both CRM Online and on-premises customers, as will Vega. It doesn’t mean all the features will be identical across deployment models but it does promise to deliver new functionality also to customers who are running CRM on their own servers. What exactly will be the delivery mechanism (Update Rollups were supposed to be clear of any new features) or how the official naming convention for different versions will evolve is not yet clear, but currently Microsoft is referring to this as the Dynamics CRM Spring Wave. Partners will have a training blitz session for this wave on April 8th/9th, so expect to see more details made public after this.

The functional changes in Leo will focus on the service module of CRM. New features showcased in the Convergence sessions included SLA management with a timer control available on the case form, merging cases and linking parent/child cases, entitlement management, email to case automation and improvements in the queue feature usability. Considering how much these new features alter the case entity functionality and configuration options, it would have surely been quite difficult to continue supporting two different feature levels if Leo would have in fact been Online only. For callcenter scenarios the new Unified Service Desk (USD) will offer functionality similar to what has previously been delivered via components like the Customer Care Accelerator (CCA) or User Interface Integration (UII). Expect to see also other feature enhancements or tools released as a part of Leo that will not be customer service specific, as well as new capabilities for CRM Online subscription management.

The contents of the Vega release had not really been disclosed prior to Convergence 2014. As this release is still further away in the future the details are not yet as clear as for Leo, but a number of very interesting enhancements to the core Dynamics CRM product were shown on the CRM roadmap slides. Calculated fields will finally be available without writing custom code, via a graphical editor with intellisense support. Business Process Flows (BF) will be enhanced with support for branching processes. On the UI side we can expect to see built-in capability for visualizing account hierarchies. These three features all address very common scenarios that Dynamics CRM customers require in their system implementations, so it’s great to see them introduced as configurable features that a system customizer can leverage right out of the box.

Social

Remember when Microsoft bought NetBreeze one year ago? Their service has now been integrated into the Redmond product portfolio and carries the name Microsoft Social Listening. Last month it was announced that Microsoft Social Listening will be offered as part of the CRM Online Professional licenses at no additional charge, whereas on-premises customers can get it for an incremental cost. This “incremental cost” was later specified to be $20 per user per month for CRM Professional CAL holders. So, while it’s not free for everyone, the pricing is still in line with Microsoft’s previous announcements of wanting to “democratize social” and integrate it as just another channel into their CRM product. (more…)

March 9, 2014
Bringing Customer Service Back to CRM with Parature

In case you missed the big news last week, Microsoft has acquired a company called Parature. Similar to the two marketing related service providers MS has bought earlier, Marketing Pilot and Netbreeze, this latest acquisition is intended for expanding the footprint of Dynamics CRM on the customer service side.

It’s been no secret that this was the next area where Microsoft was looking to build up some new capabilities for Dynamics CRM. Thinking about the existing feature set for customer service scenarios in the product, we basically haven’t had any significant enhancements to the service module since CRM 3.0. Sure, the recent platform enhancements on the process automation and UI side can be leveraged in customer service as well, but in terms of specific out-of-the-box functionality that would be aimed at helpdesk scenarios, it’s been pretty quiet so far. Case management and queues for email routing have been very useful features for many organizations using Dynamics CRM. Service scheduling and knowledge base articles… well, not so much.

The world around CRM software has changed quite a bit from 2005 when CRM 3.0 came out. Not only have online service portals and support content websites become incredibly affordable for any company to set up via cloud based services like Zendesk, but the customers of those companies have also been given a whole range of independent social channels to reach out to one another. These days the customers are in charge of the conversation, which means that if you don’t offer a forum for them to submit feedback and questions, they’ll just set one up for your brand on GetSatisfaction on their own. Regardless of how many 1-to-1 contact points you offer them, they’ll still go and share their frustration over on public channels like Twitter.

This is obviously not a world where back-office applications like traditional CRM systems that mainly offer features to your employees instead of the end customers provide a very comprehensive solution for customer service management. Sure, integrating with the customer account details, managing the support ticket process and collecting information about past interactions are all essential components of customer service in the new world, too, but they are becoming relatively less and less significant factors in the processes needed for delivering great customer experiences. When the customers no longer pick up the phone to call you when they have a problem but rather use it to search for answers on their own, call center automation software isn’t the area you should primarily be looking to invest in.

Integrating the customer facing components of modern online customer service solutions to the internal CRM systems has been the way to build systems that are up for the challenge presented by the age of the social customer. While system integration is a natural part of any CRM implementation project, requiring each organization to come up with their own solution of how to put the pieces together isn’t perhaps the most effective way forward. For example, Parature had already launched their integration with Microsoft Dynamics CRM Online back in 2009, but how many people were actually aware of it? I might have stumbled across Parature a few times before, but they certainly didn’t occupy a space on my top-of-the-mind list for possible solutions to suggest to companies using Dynamics CRM. Merging these services into Microsoft’s Dynamics CRM offering is certainly going to expose them to a potential customer audience of a completely different scale. (more…)

January 12, 2014