What’s new? Feedback and ratings on entities

With Microsoft Dynamics CRM Online 2016 Update 1 and Microsoft Dynamics CRM 2016 Service Pack 1, we now have an option to track feedback and ratings from customer for records in CRM with the click of a check box.

  • A new option appears on general tab on an entity customization form called “Feedback” which once checked creates an 1:N relationship of that entity with feedback entity similar to activities.
  • Users can use this entity to enter their response.
  • Feedback entity itself is customizable.

You can enable feedback on entities to allow customers to write feedback or provide ratings for any entity record.

Scenario: Business wants to track feedback received from customers on the customer support experience. In this case you can enable feedback for the Case entity to receive feedback.

In case of multiple ratings against one particular record, with use of simple rollup field the ratings can be consolidated.




OnLoad event for SubGrid in CRM 2015 Update 1

Till CRM 2011 we used to use Xrm.page.getControl(“grid”) to get a grid control available on form and perform any runtime activity like changing the view/query, etc. Also we were required to write the complete script on OnLoad even of form and add a timeout till the subgrid is loaded as subgrids are loaded asynchronously after the form is loaded. There was no way we can have a trigger on load of a subgrid till CRM 2015 Update 1. What we used to do is explained in older post here.

But with CRM 2015 update 1, we now have an option to execute scripts when data is loaded in subgrids. Because of which we are not required to have any timeout added in the script and iterate it till the data is loaded into subgrid.

With addition on GridControl.addOnLoad method, we can now add event handler for OnLoad event of subgrid which is more reliable than the form OnLoad event for form with a timeout. This event will get triggered whenever data is bound to a subgrid.

The steps to add this event is not similar to adding a form OnLoad event (from form customization popup), the way to add it is by invoking it using a code from other events (e.g. form OnLoad) by making use of GridControl.addOnLoad method. Similarly, use GridControl.removeOnLoad to remove event handlers.






DID YOU KNOW? List component for SharePoint integration deprecated with CRM 2015 Update 1

[Referencing The Microsoft Dynamics CRM Blog]

The Dynamics CRM to SharePoint integration has always been a key solution to document management within CRM.  With two currently available solutions, the List Component and new server-based SharePoint integration, CRM is pleased to focus our efforts on the server-based integration.  Dynamics CRM 2015 Update 1 will deprecate the List Component as a result of SharePoint’s deprecation of the sandbox solution, a dependency of the List Component.

Customers with List Component are advised to upgrade to the server-based SharePoint integration.  With CRM 2015 Update 1, server-based integration gains hybrid support between CRM Online and SharePoint On-Prem.  In a subsequent release, CRM will support CRM On-Prem to SharePoint Online and CRM On-Prem to SharePoint On-Prem.  SharePoint Online or SharePoint Server 2013 SP1 and above is required for server-based integration.

DID YOU KNOW? You can update owner and status with a single Update request in CRM 2015 with Update 1

Before CRM 2015 Update 1 release, specialized messages were required to update certain entity attribute values. These were AssignRequest to change owner of a record, SetStateRequest to change status of a record, SetParentSystemUserRequest, etc. In this release, UpdateRequest can now be used to set these attributes.

Thus with Update 1 release following specialized message will be deprecated.

  1. AssignRequest
  2. SetStateRequest
  3. SetParentSystemUserRequest
  4. SetParentTeamRequest
  5. SetParentBusinessUnitRequest
  6. SetBusinessUnitRequest
  7. SetBusinessEquipmentRequest
  8. SetBusinessSystemUserRequest

These specialized messages will continue to work with the 2011 endpoint. However, the recommendation is to use the UpdateRequest or Update method when possible to set these attributes. The Update message simplifies the SDK API and makes it easier to code standard data integration tools used with Dynamics CRM. In addition, it is easier to code and register a plug-in to execute for a single Update message instead of multiple specialized messages. The AttributeMetadata.IsValidForUpdate property for the above listed attributes has been changed to true in this release to enable this capability.

For plug-ins, when update requests are processed that include both owner fields plus other standard fields for business owned entities, plug-ins registered for the Update message in pipeline stage 20 and/or stage 40 execute once for all non-owner fields, and then once for the owner fields.

For workflows, when update requests are processed that include both owner fields plus other standard fields, workflows registered for the Update message execute once for all non-owner fields, and then once for the owner fields. Workflows registered for the Assign message by users continue to be triggered by updates to owner fields. When update requests are processed that include both state/status fields plus other standard fields, workflows registered for the Update message execute once for all non-state/status fields, and then once for the state/status fields. Workflows registered for the Change Status step continue to be triggered by updates to state/status fields.

New naming conventions for Microsoft Dynamics CRM updates

From Microsoft Dynamics CRM End User Team:

We’re changing the way we name product updates to make things simpler and to unify our approach for Microsoft Dynamics CRM Online and Microsoft Dynamics CRM (on-premises).

Finding and understanding version numbers

To understand the new naming conventions, let’s first take a look at version numbers in CRM.

To find your version number, in the upper-right corner of the web client, choose the Settings icon, and then choose About. You’ll see the following screen:

The first three numbers of the 7-digit version number tell you most everything you need to know about which version you’re working with, whether you’re using CRM Online or CRM (on-premises):

So what’s changed?

Three things have changed in regard to naming conventions:

  • CRM Online. Product names for minor releases of CRM Online will now include the year as part of the name. For example, the spring release of CRM Online for 2015 is CRM Online 2015 Update 1. If there’s an incremental update that applies to the minor release, it will be appended to the name. For example, the first incremental update to the spring 2015 release would be called CRM Online 2015 Update 1.1.
  • CRM (on-premises). In the past, incremental updates for the on-premises version of Microsoft Dynamics CRM were called “Update Rollups”. In the future, Update Rollups will just be called “Updates” and will be associated with the third digit of the version number. For example, the first incremental update for version 7.0 is CRM 2015 Update 0.1. The complete version number in this case is 7.0.1.xxxx, which indicates that the update applies to the major 7.0 release, not a spring release. There will not be a spring 2015 release for the on-premises version, but if there’s a minor fall release, it would be called CRM 2015 Update 2, and any subsequent incremental updates would be appended to that number.
  • CRM for phones. The new phone app introduced with CRM Online 2015 Update 1 will be called CRM for phones. The CRM phone app for CRM 2013 and CRM 2015 will now be called CRM for phones express.

Product names, versions, releases, and code names

The following table shows CRM Online product names with their associated version numbers and code names.

Product Name



Release or


Microsoft Dynamics CRM Online Fall ’13 6.0.0 Major release “Orion”
Fall ’13 6.0.1 Incremental update None
Fall ’13 6.0.2 Incremental update None
Spring ’14 6.1.0 Minor release “Leo”
2015 Update 7.0.0 Major release “Vega”
2015 Update 1 7.1.0 Minor release “Carina”

The following table shows CRM (on-premises) product names with their associated version numbers and code names.

Product Name



Release or


Microsoft Dynamics CRM 2013 6.0.0 Major release “Orion”
2013 UR1 6.0.1 Incremental update None
2013 UR2 6.0.2 Incremental update None
2013 SP1 6.1.0 Minor release “Leo”
2015 7.0.0 Major release “Vega”
2015 Update 0.1 7.0.1 Incremental update None

We hope this blog demystifies naming conventions for CRM going forward!

Incremental update for Dynamics Marketing

Microsoft have added two small, but important, new features to Dynamics Marketing.

  • P3P privacy policy support: This helps make sure that Dynamics Marketing website-tracking cookies will be accepted by a wider range of browsers. To use this feature, you must read, accept and enable Microsoft’s default P3P policy.More information: Cookies and privacy issues.Please refer below screenshot
  • Customer-driven update (CDU): This gives admins better control over when new updates of Dynamics Marketing will be rolled out for your organization. As Microsoft Dynamics Marketing is an online service, most of the technical details of keeping it updated with the latest features and fixes are handled by Microsoft Support. However, the update process will cause a small amount of downtime (usually less than 30 minutes), and users at your organization may also need some time to get used to the new features. Therefore, user will be notified by email well in advance and are able to control the roll-out schedule for your organization’s Dynamics Marketing update so user can plan as needed and make sure that the update does not occur right in the middle of a critical event or campaign.More information on CDU: Manage Dynamics Marketing updates

For other new features introduced in the last major update of Dynamics Marketing, please refer below link


[Resolved] Windows update for CRM Server (KB2995029) : 5.0.9690.4166

[Update 27th May 2015]: It turned out to be an hot fix provided by Microsoft support for one of the bug with service activity on update to UR 17. Thanks to Microsoft Community for a quick path.


I recently faced an issue when I was trying to import a CRM 2011 organization from a database back-up created from a existing organization on other server. I ended up with the below error.

The organization database version is not supported for upgrade.

It sounds to be a know issue were the update roll-up versions installed on source and target CRM server are different. But strange thing was the source as will as target Microsoft Dynamics CRM server had UR 17 installed. The only change was the version numbers for the web server.

Version/build number for UR 17 is 5.0.9690.4150 and that for UR 18 is 5.0.9690.4376 and what i had for web server was 5.0.9690.4166. What kind of update was this as I only had UR 17 installed and nothing else.

On bit research found a windows update installed on web server with name “Update for Microsoft Dynamics CRM Server (KB2995029)” with build number “5.0.9690.4166”. So now i had the issue resolved as i know from were did the new version came.

Image 004

But wait a minute, I’m not done yet. I ran a check to find available windows update on my target CRM server for finding the missing windows update. But as all things were going wrong, check for windows update didn’t returned the update that i was looking for.

I thought i will search for the update on web and install it manually, but hard luck there too. Microsoft had stopped providing that particular update for some reason still unknown to me. Even the KB2995029 article was removed.

I was required to manually uninstall the update from source server and then create database backup and import it. But still the question remains what the update was and when it was rolled-out why it was removed?

JavaScript methods do not trigger on update of business required fields to blank : CRM 2013 UR 3

Recently I came across a peculiar issue while running a java script on change of a mandatory (Business Required) field. JavaScript used to fire on update of perticular value but not if i change the value for the field to blank. Even debugger was not hit even though everything was correct.

On research came to know that this is a known issue and will be fixed by Update Rollup 3 for Microsoft Dynamics CRM 2013.

Below are more details on same: