Archive for the ‘MS Dynamics CRM’ Category

Microsoft Dynamics CRM 2011/2013/2015 (CRM Online) User Settings Tool

July 21, 2015

User Settings Tool is a tool for Microsoft dynamics CRM 2011/2013/2015 (CRM Online) that helps to update user personal settings in bulk. It includes the next tabs:
a) General.
b) Activity.
c) Email.
d) Privacy.
e) Languages.

Main Features:
1. It looks like CRM 2015 setting window.
2. Contains Display Names.
3. Shows user(users) settings on select.



Microsoft Dynamics CRM 2015 Asynchronous Batch Process Solution

July 20, 2015

This project’s purpose is to supply an asynchronous batch processing solution for Microsoft Dynamics CRM 2015 in all deployment types.

The provided solution allows implementing business logic operations in a scheduled reoccurring manner.

Here are some of the business problems this solution can help solving:

– Check the due date for all open Cases once a day and set ‘Exceeding SLA’ indication if due date has passed
– Send monthly news letter automatically to target customers
– Update MSCRM Users details from Active Directory once a day
– Once a month, disqualify all leads that has no open activities

The solution implements the Asynchronous Batch Process Pattern which is described in the following posts:

Asynchronous Batch Process Pattern – Part 1
Asynchronous Batch Process Pattern – Part 2
Asynchronous Batch Process Pattern – Part 3

This version is described here:

Asynchronous Batch Process Solution Revisited – part 1

MS Dynamics CRM 2015 Manage auto-save

May 25, 2015

Auto-save helps people focus on their work without having to manage saving data in the form. Most people will appreciate not having to explicitly save data each time they update a record, but some organizations may have customizations that were designed expecting an explicit save. For these organizations there are options to manage how auto-save is applied.

How auto-save works

By default all main forms for Updated Entities will have auto-save enabled. After a record is created (initially saved), any changes made to a form will automatically be saved thirty seconds after the change is made. If no changes are made in the form, the automatic save won’t occur while the form is open. After a change is made the 30-second period before an auto-save begins again. The field that someone is currently editing isn’t included in an auto-save. If someone else has updated the same record while you’re editing it, those changes will be retrieved and displayed in the form when auto-save occurs.

With auto-save enabled, the save button only appears for the initial save of the record. After the record is created, the save button in the command bar isn’t shown, but you can see a Auto save button button in the lower right corner that will show if there are any unsaved changes. This control is also displayed if auto-save is disabled.

You can click this button to save the record and refresh data in the form immediately. When auto-save is enabled the record will be saved whenever you navigate away from a record or close a separate window displaying a record. There is no need for the Save & Close button that appears in forms for entities that aren’t updated.

Should you disable auto-save?

If you have plug-ins, workflows, or form scripts that execute when a record is saved, they’ll run each time auto-save occurs. This might lead to undesirable behaviors if these extensions weren’t designed to work with auto-save. Whether auto-save is enabled or not, plug-ins, workflows, and form scripts should be designed to look for specific changes, and shouldn’t execute indiscriminately for each save event.

If you have auditing configured for an entity, each save is treated like a separate update. If someone lingers on a form with unsaved changes for more than thirty seconds, you’ll see an additional entry only if they add more data after the auto-save is performed. If you have reports that depend on auditing data and treat each save as an individual “touch” of a record, you might see an increase in the frequency of touches. If you are using this approach, you should consider that individual user behaviors make it an unreliable metric with or without auto-save enabled.

Go to TechNet article

Upgrade Process from MS Dynamics CRM 2011 to MS Dynamics CRM 2015

May 18, 2015
  1. Create a brand new CRM 2013 environment. Since the CRM 2013 deployment is only temporary, the CRM 2013 deployment can be created as a virtual machine. CRM 2013 trial product key can be used, as this is a temporary setup.
  2. Create a brand new CRM 2015 Deployment.
  3. Take the Microsoft Dynamics CRM 2011 production deployment offline
  4. Export the organization database backup from the CRM 2011 environment.
  5. Restore the database in the CRM 2013 environment, using the sql server utility.
  6. Import the organization on the CRM 2013 using the deployment manager.
  7. Verify the upgraded CRM 2013 organization.
  8. Export the organization database backup from the CRM 2013 environment.
  9. Restore the database in the CRM 2015 environment, using the sql server utility.
  10. Import the organization on the CRM 2015 using the deployment manager.
  11. Verify the upgraded CRM 2015 organization.
  12. Import the solutions with refactored code.
  13. Perform validation to ensure the system is working as expected.

MS Dynamics CRM String Workflow Utilities

May 14, 2015

Custom workflow actions that deal with text strings in Dynamics CRM 2011, 2013, & 2015

Create Empty Spaces
Regex Match
Regex Replace
Word Count


MS Dynamics CRM Numeric Workflow Utilities

May 13, 2015

Custom workflow actions that deal with numeric values in Dynamics CRM 2011, 2013, & 2015

Random Number


Microsoft Dynamics CRM 2015 Update 0.1 (KB 3010990)

May 7, 2015

Microsoft has released Microsoft Dynamics CRM 2015 Update 0.1 This is a tested, cumulative set of updates for Microsoft Dynamics CRM 2015. It includes performance enhancements that are packaged together for easy deployment.

Go to Download Center

A Custom Entity Icons solution for Microsoft Dynamics CRM

April 6, 2015

A Custom Entity Icons solution for CRM 2011, free to download and use

In this and other posts you will find the latest information regarding Microsoft Dynamics CRM and occasionally other Dynamics solutions. The focus is on general news and tips for the intrepid CRM Administrator, as well as something for even the newest CRM user. Enjoy!

In your quest for CRM customization glory, there are times when you need the perfect icon graphic for your brand new custom entity.  The normal procedure for custom entity icons is time consuming, and requires some graphic editing skill.

Generally the steps to build custom entity icons are as follows:

Browse open source icon galleries online for the appropriate icon (preferably in PNG or GIF format)

  1. Edit the icon in an image editor to resize it in 3 separate files:
    1. For image editing I recommend the free Paint .NET software
    2. Small:  16 x 16 pixels
    3. Medium:  32 x 32 pixels
    4. Large:  66 x 48 pixels
  2. Upload the 3 files to a new or existing solution in CRM 2011 as a web resource
  3. Open the custom entity in the Settings > Customizations section (or solution)
  4. Click on the “Update Icons” button
  5. Apply your icon web resources to the custom entity
  6. Publish your customizations
  7. Clear your browser cache and refresh CRM to see the new icons

I’ve been there and felt your pain.  Rather than using precious consulting time on image editing, I decided to group 22 of my custom open sourced icons in a solution file to share.  A link to download is below…


Please note this is a managed solution file, meaning  it can’t be modified.  If you want to add your own custom icons, I suggest you create a new unmanaged solution.

The included icons are in PNG format, and were procured from free and open source websites.  I included a variety that will hopefully address different industries and needs.

With this solution file, the new procedure is easier!

  1. Upload the managed solution file to CRM 2011
  2. Open the custom entity in the Settings > Customizations section (or solution)
  3. Click on the “Update Icons” button
  4. Select and apply your icon web resources to the custom entity
  5. Publish your customizations
  6. Clear your browser cache and refresh CRM to see the new icons


Import a solution from MS Dynamics CRM 2011 to MS Dynamics CRM 2015

April 1, 2015

If you keen on trying CRM 2015 and not willing to choose the upgrade path of CRM 2011-> CRM 2013 -> CRM 2015…. then you are not alone…
When you try to import the solution you will get an error saying the solution cannot be imported from CRM 2011…
Since the solution file is a mere XML, as a developer, I wanted to play around it..
This is what I did. I changes the customization.xml and updated the xml header like below.

<ImportExportXml version=”7.0.0000.4013″ SolutionPackageVersion=”7.0″ languagecode=”1044″ generatedBy=”CrmLive” xmlns:xsi=””&gt;

generatedBy=”OnPremise” for MS Dynamics CRM  On Premise

generatedBy=”CrmLive” for MS Dynamics CRM On Line

Sometimes it will not be possible to import your solution this way, due to breaking changes in the solution file. In those cases you could follow these steps:

  1. Import your solution in a clean CRM 2011 organization.
  2. (If needed) upgrade your CRM deployment to the most recent rollup update for CRM 2011.
  3. Upgrade your deployment to CRM 2013.
  4. Upgrade your CRM deployment to the most recent rollup update for CRM 2013.
  5. Upgrade your deployment to CRM 2015.
  6. Export your solution.
  7. Import your solution in your target CRM 2015 organization.

If the solution import does not complain about the validity of your solution, you should be safe to proceed. The import does its checks on the customization xml, so it can not damage your target organization.

Integration Tool for Dynamics CRM 2011/13/15

March 6, 2015


The Integration tool is an etl-tool for Dynamics CRM which allows you to insert and update records in Dynamics CRM.

Documentation: The Integration Tool Tutorial can be found on this website!

  • If you find any errors, please post them under issues.
  • If you require any features, please post them under issues with the type feature.
  • If you have problems using the tool, please post under discussion.


The tool is made up of modules (red in the graphic below), so that it will be easy to extend it with new functionality.

IntegrationTool Architecture.png

Currently the tool supports the following types of modules:

  • Connections
  • Sources
  • Transformations
  • Targets

Each module is capsuled within an assembly, that implements the complete functionality of a module like the configuration-window and the execution-method. As entrypoint it must provide a class implementing the IModule-interface.



Get every new post delivered to your Inbox.

Join 30 other followers