Found more than one RibbonDiff entity

Rajeev Pentyala - Microsoft power platform blog

Other day when I was trying to edit my ‘Account’ entity ribbon using ‘Ribbon Work Bench’ tool, I was getting ‘Found more than one RibbonDiff entity’error at the time of publishing customization’s.

Refer the KB Article


  • One of the reason could be, In <RibbonDiffXml>  there might be more than one  element with same ‘Id’.
  • In my case, I had two <HideCustomAction> node with same ‘HideActionId’


To fix the issue I followed below steps

  • Create a solution with the affected entity and export
  • Extract the folder, open the “customizations.xml”
  • Go to <RibbonDiffXml> and check if any of the XML elements with same Id’s
  • Delete or Rename the duplicate XML elements
  • Save, Re-import and Publish the solution

Note –

If by following the above steps in ‘Fix’ does not solve the problem, try these steps

  • Take a backup of “customizations.xml” file
  • Now open the original ‘customizations.xml’ and clear…

View original post 80 more words

Languages in Microsoft Dynamics Marketing

There are currently ten languages available for Microsoft Dynamics Marketing.


They are:

  1. English
  2. Danish
  3. Dutch
  4. Finnish
  5. French
  6. German
  7. Italian
  8. Portuguese
  9. Spanish
  10. Swedish

One can also import various languages in Microsoft Dynamics Marketing. To import a language, you can click the import button, and then browse to the import file and finally click import. The language will start to come in.

One can also take the languages and export by clicking export. You can also reset any customization you made in any language by clicking the reset customization box.

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:




Timer control in Microsoft Dynamics CRM 2013

This great little feature is a new control which you can place on any customizable out of the box or custom entity form. They can also be added to Quick Create and Quick View forms.

This visual indicator will let the user know how many hours/minutes/seconds remain, or have been exceeded against the specified defined failure date/time field. The visual indicators are different colors based on the status and are in large text on the form which is an excellent way to let the user know exactly where they stand against the deadline.

green red

Below links provide few examples that any business user could leverage a timer for to help keep them on track with their time sensitive tasks.

“The import file is invalid. XSD validation failed with the following error” on Solution Import to Dynamics CRM

Just had this error while trying to import a solution to Dynamics CRM 2013. On checking the log file I found that the error was with regard to a chart. It was easy to see which chart it was in relation to, so what was the issue?

Fortunately the log actually stated where the issues was. There were spurious characters in the XML, specifically “&gt; or >, but it was being viewed as text. Not sure what happened there.

I opened up the Customisations.xml in the solution file, found the offending characters, deleted, saved and imported with success. 🙂


Customize Dialog box in Dynamics CRM

Many times we face a requirement where we are asked to customize a dialog box in CRM, either with the help of JScript or HTML page. But Dialog are not available for client side extensions except custom assemblies. You cannot use JScript to Customize a dialog.

But there is always an UNSUPPORTED way:

You can customize the CRM 2011 Dialog page by customizing the page that run the dialog, the page is existing under the folder

$Microsoft Dynamics CRM Installation Folder$\CRMWeb\CS\dialog\rundialog.aspx , but it is not a recommended solution.

You can write some scripts to customize the dialog, but be careful when install a hot-fix that replace this page with default one, so keep a backup for this page on your solution after you customize it.

CRM 2013 removed the Convert Lead dialog box

CRM 2013 has removed the “Convert Lead” dialog box from the Lead Qualification process. Thus the product now doesn’t give the options of controlling which entity records to create upon Lead qualification.

New Lead Qualification process of CRM 2013 directly creates all the three entity records – Account, Contact and Opportunity as a part of lead qualification process, thus removing the flexibility from the user of selecting the entity records that needs be created. The product however checks for possible duplicates for Account and Contact records but the process isn’t favored by many and the risk of creating duplicate records or associating lead and opportunity to incorrect Account/Contact cannot be neglected.




I managed to find a good workaround to this problem and get the original functionality that we had in CRM 2011, though not the dialog. The approach suggested by is to add the Status Reason field to the form and add a Status Reason of ‘Convert to Account’ (or ‘Convert to Contact’, or both). The user then simply changes the Status Reason and a workflow takes care of the rest.

Using this approach you can build in practically any qualification behavior you want. In the case of a Lead to Account conversion, you create the new Account, link it to the Lead and then change the Lead to Qualified. The workflow is relatively simple and easily adjustable down the track if the business processes change.

If you wish to hide the original Qualify button, consider a tool like the Ribbon Workbench. Also, you can combine the best of both worlds and put some code behind a cloned Qualify button which calls an Action. This combines the elegance of a button replacement with the flexibility of workflow configuration.

Migrating history information while data import in Dynamics CRM

When you import historical data in Dynamics CRM, you may want to override property information like Created By, Created On, Modified By, Modified On associated to the record. It seems possible because CRM has provided security privileges called “Override Created on or Created by for records during data import”. However, simply update the appropriate Security Role to enable this privilege does not completely meet all requirements to override such fields as the name sounds.

The truth is, only “Created On” field can be overridden and only if the ‘allow creating duplicate records’ option is checked during the import process. In other words, we cannot update this field on existing records. Only creating new records does work for overriding “Created On” field.
While the Created By, Modified On, Modified By fields cannot be updated once the data is imported even though the user has full privilege on “Override Created on or Created by for records during data import”.

A workaround for such request can be to have a plugin that fires on pre-create of the entity and set the values for remaining fields problematically.



It is recommended that you do an import process by a administrative user which has a timezone set to GMT/UTC.

The reason is in 2005 (2005 revision to dates of observance) the date when Daylight Savings Time starts and ends in the US was changed. As a result, if you import the data back in for previous years as a user that is not on GMT, some of the records will be off by an hour.



  • When one have a list of related entities for which data import is required, order in which data for these entities are imported is important. In some cases, you have many relationships, and you cannot practically determine the order in which they should be imported. In this case, do a two-pass operation.
  • It is recommended to map the record ID/GUID fields when the records are imported. If you map the GUID fields, all relationships will work when imported.
  • It is recommended to map createdon to overriddencreatedon. You can only populate this when the record is created, and this is what will set the created on date for the record to match the original version.
  • There are some fields that you do not want to map, such as version number, import sequence.
  • There are several fields that you cannot import like modified by, created by, modified on.
  •  Custom data cannot be reimported for closed opportunities.

Navigation in Microsoft Dynamics Marketing

As Microsoft Dynamics Marketing will enhance the functionality of Microsoft Dynamics CRM Marketing module, expectation to have common users for Dynamics Marketing and Dynamics CRM in a organization is high. Thus to have similar navigation in both products is added benefit for users. Efforts made to make the navigation same in both the products are clearly visibly. We will just quickly go through main navigation available in Microsoft Dynamics Marketing.





Marketing Execution


Assets & Media








Widgets in Microsoft Dynamics Marketing

Microsoft Dynamics Marketing is coming up with some very useful widgets that can be added to home screen (similar to Dashboard in Dynamics CRM) and to side panel. These are much similar to reporting tools like drill down charts that were available with Dynamics CRM but are much enhanced. As not much information is available yet on it, below are some important points that one should know about widgets and side panel.



Untitled picture





* Widgets are components that can be added to home screen using Add Components link available on home screen.

* You can add/remove/move the widgets from/on the home screen.

* Can Maximize a particular widget from home screen and even Drill down the charts.

* Types of widgets available

1. Charts (Similar  to CRM charts)

a. Pie Chart

b. Line Chart

c. Bubble Chart

Untitled picture1

2. Budget Utilization

Untitled picture2

Untitled picture4


3. Power BI

            Untitled picture3

4. Traditional




             Untitled picture5


Side Panel

* Traditional widgets can also be added to side Panel available on right side of screen which can be expanded/collapsed.

* To add a widget to side panel, right click on side panel and select the type of traditional widget to be added.

* No other type of widgets other that traditional can be added to side panel.

Untitled picture6



We will also go over Navigation in Microsoft Dynamics Marketing in my next blog. Thanks!