Automatically creating Tags via workflow

One of the questions we are often asked is how to automatically Tag records on import/creation. It is really easy to do using the out of the box workflow capabilities in Dynamics 365.

For our example below we are going to use the Description field on the Contact entity as our source of information for processing Tags. We are going to check for two sports that will create Tag connections that will be grouped under our ‘Interests’ parent tag (having a parent tag is not a prerequisite for this process to work). You can add as many conditions as you like to the workflow to create the Tags that you need.

Step 1 – create the workflow

Navigate to Settings > Process Center > Processes and click the New button

Complete the Create Process form. We are using the Contact entity for this example but you can use whichever entity you need to associate the Tags.


Build out the steps for your workflow as follows:



For the Create Record step the Set Properties form should look like the following:



Connect To: Select the Tag record you wish to associate

As this role: Set to Tag

Expand the Details Tab and set the Connected From: in this case it is the Contact record the workflow is running on. If you are using another entity then it should be the record for that entity.


Activate the Workflow


Step 2 – Import the data or run the workflow on already existing records

Description Field on Contact:


Tags created after workflow runs:


Tagging v3.2 Released with Multi-Select Tagging Functionality

We are pleased to announce that our latest release of our very popular Tagging solution now supports the ability for users to multi-select Tags from a searchable and sortable list view.

Users simple click the down arrow icon to change the type-to-search/create area into the multi-select view:


Users then check or uncheck (removes tag if previously associated) the Tags and clicks save:



In addition two new parameters have been created:

  1. existingtagsonly – default is ‘false’. Set to ‘true’ to ensure that users can only select from existing tags even if they have the Tag Writer security role assigned.
  2. disablelistselection – default is ‘false’. Set to ‘true’ disable the ability for a user to multi-select tags from the list view. This is recommended if you have many hundreds or thousands of Tag records.


Download the latest version now – Existing license holders can upgrade at no cost!


Tagging Multiple Records with Multiple Tags in Dynamics CRM

With the latest version of Tagging (download here) we have introduced the ability to tag multiple records with multiple tags all in a single action. This functionality is provided via a new page available in the latest release. Simply select the records you wish to tag and click on the Multi Tag button:

Screen 0 - Multi Tag

Once you click on save the tags are applied to all of the records you originally selected.

Preconfigured Solution

To enable this functionality it requires you to create a button on each grid you wish to utilize multi tagging. To help kick start this for you we have provided a solution that enables this feature on account, contact and cases. Simply navigate to the Tagging page to download a copy of this solution.

Adding a button to the command bar

If you have a custom entity you wish to enable multi tagging on, or you prefer not to use the provided quick start solution, you will want to know how to add a button to the command bar. With the help of a tool called Ribbon Workbench we can easily achieve this.

1. Create a new solution and add the entity you want to customise ensuring you also add the 3 xrmc_ web resources in this screenshot:

Screen 1 - Solution

2. Launch Ribbon Workbench and once it opens select the solution you just created.

Screen 2 - Select Solution

3. Add a command to execute the MultiTag function:

  • Select the entity you with to customise
  • Right click on Commands
  • Click Add New
  • Give the command a name. For example, custom.account.MultiTag.Command

Screen 3 - Command

4. Add a new action to the command

  • Click on the lookup icon to add a new action.
  • Then click on the add button to add a new JavaScript Function Action.
  • The function you will want to call is openMultiTag
  • Select the WebResource called $webresource:xrmc_/MultiTagRibbon.js

Screen 4 - JavaScript Action

5. Add 2 parameters to this function so that it detects what was selected in the grid:

  • Click on the lookup icon beside the parameters box
  • Click the Add button and add a Crm Parameter
  • Set the value to SelectedControlSelectedItemReferences
  • Click the Add button and add another Crm Parameter
  • Set the value to SelectedEntityTypeName

Screen 5 - JavaScript Parameters

6. Add an enable rule to the command. MultiTag is only relevant if you have selected at least 1 record.

  • Click on the lookup icon beside the Enable Rules
  • Click on + Add New
  • Give it a name. For example, custom.account.MultiTag.EnableRule

Screen 6 - Enable Rule

7. Create a step for the rule

  • Click on Add Step and add Selection Count Rule
  • Set AppliesTo to Selected Entity
  • Set Minimum to 1

Screen 7 - Enable Rule Step

8. Now we can move on to the button itself.

  • Click on OK to save everything until you get back to the main screen.
  • To add a button simply drag a button from the toolbox on the left onto the appropriate command bar.

Screen 8 - Button drag

9. Give the button a name, for example, custom.account.MultiTagButton, and set the button properties as per the following settings:

Screen 9 - Button properties

Publish your changes by publishing the solution you have just edited. Note: if your changes don’t appear right away publish the solution again and refresh your browser window.

Tagging V2 – support for parent tags and synonyms

We are pleased to announce the general availability of our Tagging solution version 2.

In this release we have added two major functions – Parent Tags and Synonyms - more on each of these below.

Parent Tags

A Tag can now be designated as a ‘Parent’ which allows categorization of Tags. You are able to specify a parent tag name or names for a given Tag entry box on a record form and then only Tags in with this parent will be shown in the search results.  Tags created when a parent is specified will be created and automatically assigned to this parent. See example form below with 3 tag entry boxes each with a parent tag specified:

Parent Tags


To restrict Tag entry to a specific parent, specify the parent in the Custom Parameters section of the web resource form – this works for Tag Clouds too where you can specify to only show a Tag Cloud for the specified parent tag:

Restrict to parent


The allowable parameters for Parents are:

  1. parent – default is for Tag search results to show all Tags. Setting the parent parameter allows you to specify one or more Tags that have been designated as “parents” (i.e. they can have child tags associated to them). Multiple values can be specified and are separated by a comma.  When a parent is specified new tags that are created have this parent defined.  If there is more than one parent specified then new tags are created with a parent of the first parent specified in the list.
  2. excludeparent – default is for Tag search results to show all Tags. This option allows you exclude specific Tags which have the defined parent or parents. Multiple values can be specified and are specified by a comma. New Tags are created without a parent defined.
  3. allowparentselection – default is ‘false’. Set to ‘true’ to enable Tags which have been defined as parents for selection in the search results.

You can specify a deep hierarchical tree for your tags, however when specifying a parent in the custom parameters the Tag search results will use all Tags that are below the specified parent.


A Tag can now have a list of comma separated synonyms associated with the Tag. When a user is typing in the Tag form area, if any of the synonyms match, the Tag will be available for selection in the Tag search results.

Synonyms on tag record

Synonyms in search results

Download Tagging version 2 now!

The updated installation and user guide is available here.

How to configure Timeline for Microsoft CRM with Custom Entities

One of the most sought after additions to the Timeline was support of custom entities. This new feature opens up amazing potential to expand the Timeline and customise it to suit many different scenarios. In this post we’ll discuss how to take advantage of this functionality by adding a custom entity to the Timeline.

If you would like us to configure the Timeline for your custom entities/needs we’d be pleased to help – please email us on

Timeline Configuration

Firstly, let’s take a look at the existing configuration to give us an idea of how the timeline works. Open up the Timeline solution and from the configuration page click on the link to open the Timeline Configuration.

Screen Shot 1

You can see here how all the existing entities currently supported by the Timeline have a configuration record associated with them. Open up the appointment record to see what it contains. You’ll notice some HTML, some Fetch XML and some other settings in here.

Screen Shot 2

An important piece of the configuration is the Timeline Entity links at the bottom. These records drive how the relevant entity links to the parent entity you place the timeline on.

Adding a custom entity

Ok, let’s put this into practice and configure a custom entity to appear on the timeline. Currently my timeline looks like the following.

Screen Shot 2014-01-22 at 23.31.50

To demonstrate how the custom entity works I will configure another entity to appear on the timeline. For the purposes of this example I have installed our SMS solution and the custom entity I will add is the SMS entity (xrmc_sms). Firstly open up the Timeline Configuration record via the solution file. Hit the plus button on top of the Timeline Entities grid to add our custom entity.

A quick summary of the more important fields we’ll use are:

Entity Logical Name: xrmc_sms. This is the underlying schema name of the entity.
Headline Field: subject. The main headline that will appear on the timeline.
Date Field: actualend. The date field that drives where it appears on the timeline. If your entity is a custom activity then putting ‘actualend’ in as the date will tell the timeline to use actual or scheduled start and end dates.
Small Icon: /WebResources/xrmc_SMSIcon16x16. The small icon that is associated with this entity
HTML: The HTML that will render the custom entity record and data within the timeline. We will discuss further below
Query: The Query that is run to pull back an individual activity record. We will discuss further below

For more details on these fields you can consult the Timeline Install Guide.

How the HTML works

The HTML we are going to use is as follows:

<div class="summaryinfo">
<div class="openentity">
<a id="recordURL" href='#' title="Open full record"></a>
<p id="to" class="xRMC-Attribute xRMC-PartyList">
<p id="from" class="xRMC-Attribute xRMC-PartyList">
<p id="regardingobjectid" class="xRMC-Attribute xRMC-Reference">
<div class="innerwrapper">
<p id="description" class="xRMC-Attribute">

Let’s take a closer look at this HTML. The main thing to point out within the first 2 divs is the openentity class and the recordURL anchor. These are used to create a link back to the record for the current entity so ensure to include them in your custom HTML:

<div class="summaryinfo">
<div class="openentity">
<a id="recordURL" href='#' title="Open full record"></a>
... other fields and attributes

The next set of tags you’ll see all have the xRMC-Attribute class. This tells it that the id of this tag is an attribute on the entity. So when you put in “to” it will look at the entity and extract the “to” field.

<div class="summaryinfo">
<div class="openentity">
<a id="recordURL" href='#' title="Open full record"></a>
<p id="to" class="xRMC-Attribute xRMC-PartyList">
<p id="from" class="xRMC-Attribute xRMC-PartyList">
<p id="regardingobjectid" class="xRMC-Attribute xRMC-Reference">

Also, as you will probably know, in CRM the “to” fields are a special type called Party Lists, and regarding are references to other entities. So these have special classes to allow the timeline to handle the attributes appropriately. There are many more different types of classes you can use to display different types of fields and all are covered in the Timeline Install Guide as mentioned previously.

Query CRM for the Entity Record

The final piece of the puzzle when configuring an entity is telling the Timeline how to get the record from the database. This is done using Fetch XML. A really quick way to build some Fetch XML is using the Advanced Find to create your query and then using the Download FetchXML button. For now let’s just use the following to pull back the required record:

<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false">
<entity name="xrmc_sms">
<attribute name="to" />
<attribute name="regardingobjectid" />
<attribute name="activityid" />
<attribute name="description" />
<attribute name="from" />
<filter type="and">
<condition attribute="activityid" operator="eq" value="{0}" />

The main thing of note here is the special id parameter here:

<condition attribute="activityid" operator="eq" value="{0}" />

This will be replaced with the relevant SMS id at execution time to load the correct SMS entity record.

Linking this entity to a Timeline

We’re missing one last important link, when I place a Timeline on the Account page how does the Timeline know how to link this SMS entity to the Account entity? That’s where Timeline Entity Links come into play. If we take a look at the bottom of our Timeline Entity form you’ll see a section at the bottom for these Timeline Entity Links. Add a new one to the grid with the following details:

Name: SMS
Logical Entity Name: xrmc_sms

And put the following in as the query. It will locate all of our xrmc_sms records that are regarding a particular account:

<fetch version="1.0" output-format="xml-platform" mapping="logical" distinct="false">
<entity name="xrmc_sms">
<attribute name="subject" />
<attribute name="statuscode" />
<attribute name="regardingobjectid" />
<attribute name="activityid" />
<attribute name="scheduledstart" />
<attribute name="actualstart" />
<attribute name="actualend" />
<attribute name="activitytypecode" />
<attribute name="statecode" />
<order attribute="actualend" descending="true" />
<order attribute="actualstart" descending="true" />
<filter type="and">
<condition attribute="regardingobjectid" operator="eq" value="{0}" />

The main thing you’ll notice here is we’ve put in account for our Logical Entity Name. This tells the timeline, when placed on an account record, to use this timeline entity link.

Also, in addition to this, in the query you’ll notice that special field again:

<condition attribute="regardingobjectid" operator="eq" value="{0}" />

This will get replaced with the Account Id when it’s rendered on the account page.

Timeline with Custom Entities!

If you navigate back to an account you’ll now see SMS messages appear in the timeline:

Screen Shot 2014-01-23 at 23.16.53


The updated Timeline is supported on CRM 2013 and CRM 2011 and is available for download now.

A free version of the Timeline is still available with all the features of the previous version, but to unlock custom entities and other great new features purchase a license key today!

Timeline v2 for Microsoft Dynamics CRM released with support for custom entities

Timeline v2 CRM 2013We are very pleased to announce the new version of Timeline for Microsoft Dynamics CRM!

The no. 1 request has been to support custom entities on a Timeline and we are pleased to say that this option is now supported in the new version along with a number of other enhancements.

Timeline enhancements:

Custom entity support*

Display any entity on your Timelines in addition to the ones configured by default. We provide step-by-step instructions on how you can set this up – see the installation guide.

Timeline on a Dashboard*

It is now possible to show a Timeline on a Dashboard. The Timeline results are not bound to a specific record so you can show anything you desire from your CRM data!

Whatever query you can dream up in the Advanced find will work with your Dashboard Timeline. Show things like:

  • Your team’s Opportunities and recently closed orders
  • Cases that are due in the next 2 days – the Timeline will show you immediately if you have a bottleneck
  • Your own custom entity data – you decide!

Show only desired entities when loading the Timeline

Timelines can get busy but if there is vital information you would like to be displayed by default and leave the rest of the noise out, you can now do this. Manually add/remove Timeline by checking the entities you want displayed and click Update.

Select Entities to Display

CRM 2013 look and feel

We have updated the Timeline to fit with the new CRM 2013 look and feel – your users will think the Timeline is a part of Microsoft Dynamics CRM with its seamless integration.

Customize the queries that return timeline results*

If you don’t like the data being returned in the default Timeline set up, that’s no problem. We now let you edit, remove or add new queries to manipulate the data that will be shown to your users.

It is as simple as making your query in the Advance Find, exporting the XML using the button on the Advanced Find ribbon and pasting this into the Timeline Entity Link configuration record.

Timeline Entity Link

Customize the fields, localize labels and look and feel shown on in the Timeline detail pane (full HTML support)*

Not only do we let you edit the queries, we let you edit the Timeline detail pane as well! This means you can display any information from the selected record in the detail pane, control the layout and styling via HTML. We provide some simple to apply CSS classes to ensure that the various field types render appropriately on the screen – e.g. apply the class xRMC-Url make the text field containing a link click-able.

Using the HTML configuration you can change the labels to support a different language.

Timeline Entity


The updated Timeline is supported on CRM 2013 and CRM 2011 and is available for download now.

Timeline is now available as a free and as a paid for version. The free version supports all the functionality of the previous version.  Items marked with a * above are available in the paid version.

You can purchase a license key to unlock the great new functions.

Happy Timelining!

Top 10 Data Migration Traps

How to avoid being caught by some common traps when migrating to Microsoft Dynamics CRM.

Considering the impact on delivery dates, testing, training, regulatory compliance and budget, it is always amazing how often the complexities of migration are overlooked. There are many traps to fall into when implementing your shiny new CRM system but migration is one stick that the underlying business will beat you with. Let’s look at 1o of these traps you want to avoid:

1. Your project plan has one task that says ‘Migrate Data’.

This is very easily done as either the team developing the new system or the vendor, can’t estimate the effort so it is just left as a single item. Don’t do it. Do some analysis that will at least give you a consideration of risk, effort and cost. Without these, managing the expectation of the business will be impossible.

2. Not using an automation tool to migrate data.

In the past we have conducted migrations based on SQL scripts, batch files, custom code etc. Quickly you realise that there are real benefits to automation. For example the new system has 5 new fields in a table. Rather than going back and redeveloping the migration code, you just point the tool (we like using Simego) at it and click update. 1 hour saved and no errors introduced, commit it to source control.

3. Migrating old data that might better be placed in a reporting system.

You should always consider that some data might be better placed in a reporting or document management solution. If you have a ‘end of year’ balance brought forward into a new system, do you need all of last years transactions or can you just lookup a report showing them? Rationalising some of this data can pay dividends in the scale of your migration project.

4. You let the vendor leave out migration or worse make it your entire problem.

Migrating data is risky and can be expensive; your development team knows how their current system works better than anyone. Make sure you have some migration commitment from the vendor before agreeing the deliverables and costs.

5. Assume that the migration with be straightforward because the old system and the new system do the same thing.

The architectural requirements of systems mean that they may have completely differing internal structures and security models. These factors influence the effort of migration by factors of 10. Even simple upgrades between versions can be the same as moving to a different vendor’s.

6. Underestimate the effect of the new security model on migration.

Security models are there to make sure that data is not viewed or manipulated by an unauthorised individual. During migrations it is often necessary to circumvent or assume the identity to extract and insert data. The developers of the current systems could make it extremely difficult for you to move data by using encryption, logic in the user screens and even more esoteric (smart at the time) tricks.

7. Thinking you can sort out the data quality once it is in the new system.

Often a driving reason the move to a new system is that it has better data quality control. For example, we often see telephone numbers saved as ‘TBC’ in an old system and the new system will only allow number to be saved. A significant phase in migration is cleaning the underlying system so that clean data can be stored easily into the new system. Often if you migrate dirty data, even with the best intentions, it loses priority and remains dirty undermining the value of your new system.

8. Underestimating the involvement from the business to clean the data.

As with 7, it is important to realise that users will have to assist in cleaning data. You can make this easier by creating lists of broken records and request rules for your automation tools to follow, but the bottom line is that your users know the data and are generally the best ones to clean it up most efficiently.

9. Not realizing the impact of month/quarter/year ends or other business events on the migration.

Many accounting systems require journaling and retrospective adjustment. Additionally, when picking a date for migration, make sure the business is available and not buried in month end, quarter end, tax year-end, year end or some other business event which requires significant business focus.

10. Not documenting the migration process so no one knows where the data came from!

When migrating data it is often necessary to transform the data several times before it finally resides in the new system. Often a client will ask, why is the address used and not the billing address from the old system? You need to have a method of tracing the source to target and often your automation tools can help to generate documentation.

At xRM Consultancy we are experts at migrating data from a variety of sources into Microsoft Dynamics CRM - talk to us to see how we can help you avoid these data migration traps


This post reproduced/adapted from an original by our friends at Simego

SMS solution updated to support default country code

We have released a minor update to our SMS solution for Microsoft Dynamics CRM that allows you to set a default country code in the configuration entity. This is so that you can store local mobile numbers in your country format instead of having to store numbers in the full international format. Mobile numbers outside of your country will still need to be stored in full with the country code e.g. 00 1 212 123 123 or +1 212 123 123.

There is a new field on the configuration entity to store the default country code. The defaults to 44 (UK) if it is left blank.

SMS Configuration Default Country Code

The default Country Code is applied to mobile numbers as follows:

Default Country Code Example Number Full converted number in international format
[blank] 07712 123 123 00447712123123
44 (0)7712 123 123 00447712123123
44 7712 123 123 00447712123123
If the country code is matched it does not get appended twice)
44 +44 (0)7712 123 123 00447712123123
44 +447712123123 00447712123123
44 447712123123 00447712123123
1 212 123 123 001212123123
1 +1 212 123 123 001212123123


Download the new solution from here

Please let us know if you have any feedback.

Migrating from ACT! to Dynamics CRM

Today let’s discuss migrating data from ACT! to Microsoft Dynamics CRM 2011. The last migration we undertook from Act to Microsoft Dynamics CRM also involved a brand new tool for us called Data Synchronisation Studio from the team at Simego. At xRM Consultancy we have dabbled with a lot of data migration tools, but Simego and it’s Data Synchronisation Studio stood out from the pack this time due to some powerful features it offers. So we decided to give this a trial to see if it really was worth investing our time and money in. For this post let’s pick one part of a migration that is often a pain point: attachments. This will also allow us to explore some of the features of Data Synchronisation Studio and how it stands up to the task.

Preparing the data

First question you may ask – what exactly is ACT! underneath the hood? More importantly, how do we extract that data and get it into Microsoft Dynamics CRM? ACT! sits on top of a SQL Server database so this makes querying and pulling the data out a lot easier than having to deal with APIs or flat files. Most of the data in here is quite straight forward and you’ll immediately identify some entity tables such as TBL_CONTACT and TBL_COMPANY. Linking the data up to related tables and retrieving the relevant columns is a little more challenging.  Our strategy to ease this pain is using a set of views and functions we’ve built up over time which allows us to easily extract the relevant and linked data.

For this example let’s deal more specifically with how attachments are stored and referenced. People already up to speed with Microsoft Dynamics CRM will know that attachments are base 64 encoded and stored directly in the database. In ACT! these files are stored externally and the file name is referenced within the relevant table – TBL_ATTACHMENT. So we need to combine queries with external files. Let’s start off with an example query:


Running will get you some results like this:


As we can see from the query ACT! gives us a list of files, which includes the file name, but no path. This isn’t a problem, because there will be a folder on the server where all these files are stored. Once you find them it’s pretty much a 1 to 1 mapping from each record to a file. All we need to do is map these files to the relevant entity records we will have already imported. Let’s take a look at a basic query to link these attachments to a company record. Take the following query:

      ,[c].[COMPANYID] as [OBJECTID]
      ,'account' as [OBJECTTYPE]
inner join TBL_HISTORY [h] on [h].[HISTORYID] = [A].[HISTORYID]
inner join TBL_HISTORYTYPE [t] on [t].[historytypeid] = [h].[historytypeid]
inner join TBL_COMPANY_HISTORY [ch] on [ch].[HISTORYID] = [h].[HISTORYID]
inner join TBL_COMPANY c on [c].[COMPANYID] = [ch].[COMPANYID]

Running this will get you some results like this:


The key thing to note here is linking to the company record via a table called TBL_HISTORY. This table is a multipurpose table, but it’s main purpose could be described as keeping a record of all “history” of actions that occur against records. I’ve included the TBL_HISTORYTYPE in the query to show how to pull out a description of the type of history activity that was recorded, but this isn’t something we need to migrate. Finally, and most importantly, we can use the link table TBL_COMPANYHISTORY to pull back records that are associated with companies.

Importing the data

Now that we have these company attachment records we need to import them. Remember, there is a mixture here between table records and files stored externally on the hard drive. This is the perfect opportunity to see what Data Synchronisation studio can offer in order to fulfil this task. At a first glance it looks just like your standard data import tool:


On the left you can link up your source data, i.e. the ACT! database. As I mentioned previously we have a set of views we create in the ACT! database so let’s hook into one of those. For all intense purposes let’s say the view is called xrmc_CompanyAttachments. On the right you link to your target table, which is the annotation entity in your Microsoft Dynamics CRM organisation. You can map across most of the columns straight from the query I prepared above.


So everything apart from the file contents has been mapped. Getting Data Synchronisation Studio to read this file and import it opens up a really interesting and powerful feature of this tool, namely Dynamic Columns. Every Dynamics CRM developer who has used a migration tool will love this – Dynamic Columns are simply properties exposed using C# classes! So let’s write our property:

// Convert the pysical file to a Base64 string
public string FileContents
    string fullFilePath = "C:\\Path To Act Attachments\\" + FILENAME;
    if (System.IO.File.Exists(fullFilePath)) {
      return Convert.ToBase64String(System.IO.File.ReadAllBytes(fullFilePath));
    return string.Empty;

And you end up with the following in Data Synchronisation Studio:


Imagine the power of this. Suddenly, reading in a file becomes such a simple task. Simply build the code using the provided build button and this provides you with a new list to map to your data. Map this new Dynamic Column across to your DocumentBody and you’re pretty much done:


If we do a compare, using the Compare A -> B button, let’s take a quick look at what our data looks like:


And that’s pretty much it. Click on Synchronise and watch those file migrate!

Next time I’ll discuss a more advanced scenario where we had to merge customer data from ACT! and Sage 50 Accounts into a single view of the customer within Dynamics CRM.

If you’ve got ACT! and you are looking to upgrade to Microsoft Dynamics CRM why not get in touch with our team.

Using Tags for creating dynamic marketing lists

Once you have started using our Tagging solution for Microsoft Dynamics CRM  you will want to use that information to segment your data. A common scenario is to build a marketing list of all Accounts that have been tagged with one or more tags.

The scenario we will use in this post is as follows: We are organising a breakfast event and want to be able to quickly tag contacts that have registered an interest in coming along. Account managers will call or email clients and prospects and manage the interest by tagging the relevant individuals.

Step 1 – Adding the tag to the contact records

Once tagging has been enabled on the Contact form a user simply has to enter (or select if it the tag has already been used) “Breakfast Event July 2013″ in the Tags box.   This process is repeated over the course of the campaign.

Breakfast Event Tag

Step 2 – Create Marketing List

When your are ready to collate your list of interested contacts, create a dynamic marketing list which identifies all contacts which have been tagged “Breakfast Event July 2013″

a) Create the Marketing List

Breakfast Event Marketing ListMembers

b) Click Manage Members to build the query

  1. Select Connections (Connect From) from the Related section of  the drop down list
  2. From the next “Select” list choose Connected From (Tag) from the Related section
  3. Finally choose Tag from the Fields section of the next “Select” list and lookup the Breakfast Event July 2013 tag

Breakfast Event Manage Members

c) View the marketing list members – we have only one in this case but as users add (or remove) the tag to contacts the list will dynamically change.

Breakfast Event Marketing ListMembers

Easy huh! Tagging can be a very quick way to manage your marketing lists – use it for managing subscriptions to newsletters, product interests, partner emails….

You can download the Tagging for Microsoft Dynamics CRM solution for free!