Quantcast
Channel: Microsoft Dynamics 365 Community
Viewing all 13977 articles
Browse latest View live

Dynamics 365 Server version 9.0 available for download

$
0
0

A few days behind schedule, but the highly anticipated Dynamics 365 version 9.0 for On-Premise deployments is not available for download. Preview releases have been available for a while now via the Microsoft experience web site, but on 11/2 Microsoft made this release public.

It is now available for download on the Microsoft Download center. A 90 day trial key can be used, or if you have a commercial license key you can enter that at any time (during setup or within the 90 days trial). This version includes the Reporting extensions, just like previous version. Also, be aware of supported operating systems. The system requirement mention requirement for Windows Server 2016, but just point to the Dynamics 365 Customer Engagement document site.

Download Link


Manage CDS Entity Data – Microsoft PowerApps Office Add-In

$
0
0
Originally posted on Bansal Blogs - Dynamics 365, PowerApps, Microsoft Flows, Power BI : Microsoft PowerApps Office Add-In enables user to read, modify and insert data in CDS environment. Add-In is available...(read more)

Microsoft Dynamics 365 for Field Service - Connected Field Service

$
0
0
Hi Everyone Today i am going to discuss about the connected field services, Communication and Integration with IoT Devices. Connected Field Service 1. IOT Solution installed on top of Dynamics 365 2. Key...(read more)

How to Hit a Home Run with User Adoption After Your CRM Implementation

$
0
0

Ledgeview Partners eBookAfter you’ve completed your CRM project implementation, it’s time to continue gaining CRM User Adoption.

CRM User Adoption is arguably the most important step of any CRM implementation project.

In baseball, you can think of this step of your CRM project as building your fan base.

Without continuous user adoption, all of the other work you’ve put into your CRM project will have been wasted.

If Users fail to use your CRM system, it will fail to live up to its capabilities.

Once you implement CRM, CRM should be at the core of your business.

To help your Users see it this way, you need to communicate the “Bigger Picture” of your CRM project to them. Express how it will increase your business value.

Get them involved with your CRM project from the get-go to increase user adoption. By including them in the conversation from the start, you’re more likely to get them on board and keep them there.

By doing this, you show you respect and appreciate their feedback. Continue to encourage them throughout phases of your CRM project.

Help them to see opportunities and lessons in “failures.” You are all learning about CRM together. No one will be perfect. Mistakes will be made, but there is always a solution.

Train and retrain Users as you see fit. Schedule regular training to keep user adoption high.

Don’t just think: “Build it and they will come,” but rather, “Build it so it’s easy to use and is beneficial, and they will come!”

When users see the benefits, adoption increases, excitement builds, and your “fan base” thrives!

Allow your CRM system evolve the way it was intended to when you encourage and enable your Users to adopt it and evolve with it.


Gaining User Adoption is a comprehensive process, so Ledgeview has 5 eBooks to help you achieve User Adoption Success from the start of your project to years after, to debunking common misconceptions along the way.

Access these resources when you click the titles below:


For more tips on how to have a successful CRM Implementation, get Ledgeview’s latest eBook, “10 Steps to a Successful CRM Implementation: Preparing for a Winning Season.”

Download it here.

Ledgeview Partners eBook

Tip #1185: Customize the document grid

$
0
0

I upgraded to server side SharePoint integration and now I don’t see enough detail from the document grid. It doesn’t show me who checked out the file, and I have to open the SharePoint location to see who checked it out.

Reader

Good news–with server-side SharePoint integration you can customize the grid more than you could with the client side grid control. 

Do an advanced find of the view entity for where the name contains “Document Associated.” From there you can add a bunch of additional fields to the grid view.

(Facebook and Twitter cover photo by Stefan Schweihofer on Pixabay)

Duplicate Detection When Qualifying Leads in Dynamics 365 - Part 1

$
0
0

This blog series is about duplicate detection rules when qualifying a Lead.

When a Lead record gets qualified, the Lead gets converted to an Opportunity record, and Account or Contact records are created in the process. During the Lead Qualification process, I noticed a duplicate warning prompt that appears after I clicked the Qualify button:

image

This blog will highlight the behavior of this prompt and allow you to refine your duplication detection criteria for this process.

The currently defined and published duplicate detection rules are:

image

These are the out-of-the-box duplication detection rules defined on a freshly created Dynamics 365 instance and are configured to detect exact matches.

Testing Duplication Detection Rules

I created the Lead ‘Miguel Lead Test 1’and qualified it. This created an Opportunity, Account, and Contact record.
  image

The Account was automatically created with Account Name = “Miguel Test Ltd”.

The Contact record was automatically created with Full Name = “Miguel Test1” and Email = “miguel@test.com”.

I created another Lead record with the Contact Name ‘Miguel Test2’ and email address miguel@test.com. This conflicted with the first Lead created as they have the same email address so the Duplicates Detected prompt appears:

image

I saved it so there are 2 Leads in the system with the same email address.

I then qualified the Lead record ‘Miguel Lead Test 2’. Before the Account and Contact records were created for this Lead, I got the duplicate warning prompt below:

image

Clicking the Account and Contact lookup fields showed that there was already an existing Account and Contact record, which are the Accounts and Contact records created for the initial Lead record ‘Miguel Lead Test 1’.

image

The system was detecting that if it created an Account or Contact record via the Qualify process for ‘Miguel Lead Test 2’, they will be duplicated of the Account and Contact records which were created from ‘Miguel Lead Test 1’. This is because the Contacts will have the same email address miguel@test.com, and the Accounts will have the same Account Name ‘Miguel Test Ltd’.
 

Unpublishing Duplicate Detection Rules

I then unpublished the duplicate detection rule ‘Contacts with the same e-mail address’. Then I tried to qualify the ‘Miguel Lead Test 2’. I got the same duplicate warning error, but when I clicked the Contact lookup I got no results:

image

I then unpublished the duplicate detection rule for ‘Accounts with the same Account Name’. Similarly, when I tried to qualify ‘Miguel Lead test 2’ I got no results when clicking the Account lookup control:

image
 
I then unpublished all the duplicate detection rules including the one for Leads, and qualified ‘Miguel Lead test 2’. The duplicate warning prompt did not appear, and the Lead qualified.

In summary:
• the criteria for the ‘Duplicate warning’ prompt will only appear if the Lead record on Qualify is triggering a Lead duplicate detection rule
• the criteria for search results appearing under the Account/ Contact lookup for the ‘Duplicate warning’ prompt depends on whether the new Account/ Contact record to be created during the Qualification process is triggering an Account/ Contact duplicate detection rule, e.g. Base Type = Contact, Matching Type = Contact, Criteria = Email Address Exact Match

I hope this blog will guide you towards refining your criteria for duplicate detection during the Lead Qualification process.

Part 2 of this blog series will expand on this interesting behaviour for duplicate detection rules with different base and matching record types.

This feature was noted as of Microsoft Dynamics 365 Version 1710 (9.0.2.2074) online.

Make Power BI report using data from Azure SQL server and view in Dynamics 365

$
0
0
Introduction: In this blog, we will see how to show data of SQL server into Dynamics CRM. For this first, you need to connect your Power BI Desktop with SQL server. After that, we can show Power BI report...(read more)

Plugin on Pre-Validation Stage in Dynamics 365 CE

$
0
0
Recently we had a requirement to delete the Account record without deleting the associated Contact records. If we try deleting the account record we’d get the following message box The relationship...(read more)

Dynamics 365 v. 9 New Functionality – Virtual Entities

$
0
0

Virtual entities were introduced in Dynamics 365 (Online) version 9.0.  Virtual entities sound quite futuristic but put simply they enable integration of data stored in external systems without the need of custom code and data replication.  This blog describes the benefits of using virtual entities, how to use them and what to think about when using them.

 

The first release of virtual entities only allows Read-Only access to the data and there are a few other limitations which I have been detailed here in this post.

 

Key Benefits of Virtual Entities in Dynamics 365

  • There are no physical tables created in the database to store the data.  The data is retrieved dynamically as and when it’s needed allowing for a reduction in storage space, therefore, reducing monthly CRM storage costs.  Please note as it currently stands in the Microsoft Dynamics 365 licensing guide for Online (October 2018) as standard you will get 10GB.  For every 20 full plan users, you will receive an extra 5GB.
  • No code is required to display the external data in CRM, which reduces project costs and time.

Limitations

The initial release of virtual entities does, unfortunately, come with some limitations.  These limitations should be considered to evaluate the use of virtual entities.

 

These limitations are:

 

  • The data displayed within the virtual entity is read-only.  This means that if a user updates the data the data cannot be pushed back into the external system.
  • Only Organization owned virtual entities are supported in the current release. When creating a new virtual entity you must ensure that the ownership dropdown is set to Organization rather than User or Team as per the image here taken from Microsoft Dynamics 365.

 

  • Please note that Field Level Security is not supported in the current release.
  • If the virtual entity has been set up with ‘User or Team’ ownership then any associated security role settings for the entity are not supported.
  • Auditing of the Virtual Entity is not supported in the current release and instead will be required to be implemented within the external database.
  • Downloading the data to use offline isn’t supported at this time.  This means that data isn't visible when working offline.
  • Virtual entities cannot be configured as an active entity.
  • Business Process Flows are not supported.
  • Queues cannot be set up for records within the virtual entity.
  • Once the virtual entity has been created it cannot then be changed back to a standard CRM entity.

 

Data Modelling

A further consideration to be made when using virtual entities is data modelling.  The data which is held in the external data store must follow these rules:

 

Each entity within the external data source needs to have a GUID Primary Key associated with it. This GUID is used as the Primary Key in the virtual entity in Dynamics 365.

 

You must be able to display the external data properties as Dynamics 365 attributes, this also applies for all entity relationships.  These attributes include

 

  • Numbers
  • Single Line of Text and option sets
  • Lookups
  • Date & Time

 

As the data in the virtual entity is read-only, calculated and rollup fields are not available. If any calculations or rollups are needed these will need to be executed in the external data source.

How to create a Data Source

 

To create a new data source firstly go to Settings> Administration> VirtualEntityDataSources. From here click New in the toolbar, you will be prompted to select a Data Provider. The two options here are:

 

  • OData v4 Data Provider or
  • Solutions Component Data Provider

 

Select the appropriate Data Provider then click OK.  A new window will now appear for you to enter the Data Source information. For the purpose of this blog, I have selected OData v4 Data Provider. Populate the Name and enter the URL then add any additional Parameters as necessary.  Click Save & Close, you will now be able to use this Data Source when creating new Virtual Entities.

 

How to create a Virtual Entity

Virtual Entities can be created in the same way other entities are normally created however there are a number of additional steps which need to be fulfilled which I have listed here:

 

  1. Navigate to Settings> Customizations> Customize the System
  2. Select Entities in the pane on the left and click New
  3. Populate the entity details as standard making sure that the following items are populated:
    • Virtual Entity tick box - this needs to be ticked in order for the entity to become virtual.  This cannot be ticked once the entity has been created so be sure to tick before clicking Save.
    • Data Source drop-down - this will display a list of all Data Sources that have been created in the system. Select the appropriate Data Source, if left blank no data will be pulled through into the entity.
    • External Name – Populate this with the name of the matching table in the external system.
    • External Collection Name – Populate this with the plural name of the matching table in the external system.

 

Here is an example of a virtual entity for Suppliers which uses an OData v4 feed to pull in the information.

 

the screenshot was taken from a Microsoft Dynamics 365 site.

 

  • Now you can start creating the fields needed to display the information in D365. When creating the fields ensure the External Name is populated with the matching field name from the external system.
  • Save and publish all changes
  • A refresh of CRM may be needed for the entity to display in the Sitemap. Once CRM has reloaded you can navigate to your newly created virtual entity to confirm the data is being pulled into CRM.

 

Want to learn about other new features in Dynamics 365?  Check out our new blog about Multi-Select Option Sets.

 

This blog was written by Luke Judge a technical CRM specialist at Caltech I.T. Limited in West Yorkshire, UK.

The post Dynamics 365 v. 9 New Functionality – Virtual Entities appeared first on CRM Software Blog | Dynamics 365.

Gathering Business Requirements with the 6 Ws

$
0
0
business requirements

The 6 Ws (well, it’s actually 5 Ws and an H) are basic questions asked when gathering information. They are: Who? What? Where? When? Why? and How? Getting answers to these is integral to capturing the details when solving a problem because they require factual answers that can’t be Yes or No.

Think back to your school days. This approach was a key part of writing essays after all, if you answered all these questions, you could be assured that your essay was complete and that the reader would understand what you were intending to convey.

This approach can be useful when gathering business requirements, as well. Let’s look at each of these questions in the context of a requirements session. Recently, we were working with a paint manufacturer and interviewing their field sales representatives. These reps visit retail outlets and contractors on a regular basis to ensure product placement, check in on quality/training issues, and recommend new products to support marketing initiatives. They are required to make 30 visits a week, 40% of which should be retail outlets. To gather information, we asked the 6 Ws:

Who are you visiting?

We asked about categorization of retail outlets, the significance of one location versus others in the area, whether there was a need to contact the location for an appointment prior to arrival, etc. Answers to these questions could, for example, let us know we should be considering tracking appointments in Outlook, scheduling the maximum numbers of visits in a day, or even integrating mapping/routing to help the rep drive to each location in the most efficient manner.

What do you do when you get there?

When at an outlet, a rep performs a variety of tasks, such as checking inventory and scheduling a resupply order for products that sell the best, dropping off marketing material, and following up on a training class. They also hand out awards for monthly sales, get more information on a complaint about a bad batch of paint, etc. As we go through these questions, we may determine, for example, that a rep could benefit from a checklist of tasks to perform on each visit. Similarly, we may determine that the mobile app needs to provide an easy way to place a product order or schedule a call from the Training department.

Where are you working from?

The reps benefited from being online while at the location, although some preferred to enter notes, orders, etc. at the end of the day. This information helped us determine how robust the mobile app needs to be. Depending on the answers, we may, for example, end up advising the customer that reps could benefit from tablet devices.

When do you visit?

It may sound trivial, but things like working hours and vacation/holiday schedules all impact the system. Additionally, knowing the hours the system is expected to be available helps us when scheduling deployments.

Why did you visit this location?

Again, it may seem trivial, but taking into consideration reasons – things like a rep always visiting the biggest customers on the 1st Wednesday of the month or the fact that some visits are the result of following up on a training class – could ultimately help with scheduling. More importantly, understanding what the rep is supposed to be doing on a daily/monthly basis can help us be more strategic with the system and devise ways to use enterprise information to schedule visits for a rep.

How do you manage your visit?

This is where we shine. If they’re in a technological desert, where they take notes on paper and transcribe them into some system at the end of the day, we can devise intuitive, easy-to-use mobile or online forms to help them capture this information, along with quick tools (product order, schedule training, etc.) that can save time. Even if they’re already using D365, we can learn what changes/additions will help them daily.

Most of us are probably already asking these questions in some form or another, but it’s interesting that such an ancient method of information gathering (the usage of these questions have often been ascribed to Aristotle) still applies to our modern world and the art of business requirements for software development.

Be sure to subscribe to our blog!

Happy Dynamics 365’ing!

Different Updating Instance status during Dynamics 365 Upgrade

$
0
0
The day has come when we had scheduled the upgrade of our Dynamics 365 instance Test Instance(from 8.2 to 9.0). We can see the below message during the scheduled time à “The update will being within...(read more)

Sales General Availability Updates from the Microsoft Dynamics 365/CRM October Release

$
0
0

Microsoft Dynamics 365/CRM

With any Microsoft Dynamics 365/CRM Release, there is a lot to learn, and October 2018 updates are no exception.

You may have already read blogs from us about it, but this one will give you more key takeaways you should know about as a user or admin!

Before reading, you may want to check out:

Then, when you’re ready, let’s dive into more key General Availability updates from the October Release you should know about …


1. Playbooks
Playbooks are a new capability/feature in Microsoft Dynamics 365/CRM as of the October Release that are designed to “help organizations automate repeatable sales activities and respond to external events”.

Playbooks are predictive and event-driven guidance systems that suggest the next best action items for salespeople to take within their CRM system.

There’s no doubt that we are living in the age of the consumer, and, as we become more aware of buyer behavior, as sellers, we must become more responsive to it.

Playbooks offer this, as they are reactive process-driven repositories.

Microsoft helps to put Playbooks into context – So, for example, if a key decision-maker leaves the project in the middle of a deal, this may jeopardize the transaction, but Playbooks can help you trigger a play that creates a set of tasks or actions needed to remedy the situation.

Playbooks help you carefully orchestrate your activities to ensure your process and strategies are successful.

Microsoft says Playbooks will allow organizations to:

  • Configure Playbooks and define the set of tasks and activities to automate once triggered
  • Search and launch Playbooks for a particular scenario
  • Track the status progress of running Playbooks against their outcome, successful or not

2. LinkedIn Insights
Any business process in CRM can be created or enhanced to include LinkedIn Insights about people and companies.

Insights allow the user to complete stages more accurately and quickly; thus, driving sales through to completion.

LinkedIn Insights include ample information about your customers, prospects, and leads; plus, it provides other functionalities beyond that to help your salespeople become even smarter sellers with CRM.

Here’s some of the information you’ll discover while using LinkedIn Insights, in your CRM system:

  • Size, Industry, and Location Data about Companies
  • Company, Position, and Years of Experience the individual target has
  • Icebreakers and Conversation Starters to create warm introductions with your customers
  • First, Second, and TeamLink connections to provide warm introductions as they traverse the entire organization and the aggregate networks
  • Recommendations for people who are “similar to” a target, lead, or prospect that plays a key role within their organization

You can learn more about LinkedIn Sales Navigator here.


To keep up with key Microsoft Dynamics 365/CRM updates and insight, be sure to join us for our next user group webinar.

Register when you click on the image below.

Microsoft Dynamics 365 CRM User Group Webinar

Key New Technologies Showcased at the 2018 #UserGroupSummit

$
0
0

Ledgeview CRMUG

Last, but certainly not least, there were A LOT of great technologies showcased, and much to take away from them, from the 2018 CRMUG #UserGroupSummit.

Within this post, we uncover two main ones that Dynamic Communities should know about before moving into 2019.

If you haven’t already read about our other key takeaways, we suggest covering them first, before you dive into this post …

Then, when you’re ready, let’s dive into the important tech talk that was covered throughout the summit in Phoenix, AZ earlier this October …


1. SimpleChat
SimpleChat is a native omnichannel solution that is supported by Act-On Marketing Automation Technology.

The company that created SimpleChat is based out of Israel, called the Elad Group, and they are a Microsoft Dynamics Gold Partner.

Core features of the new technology include:

  • Customer authentication is done automatically with CRM Data
  • Conversations are automatically documented
  • Customer timeline histories are easily accessible
  • Chatbot is included
  • Chat Router is included
  • Multiple Conversations can happen at once
  • Social Media Monitoring is included
  • Instant Messaging (IM) to Facebook Messenger or Twitter is included
  • Outbound Chats are possible
  • Easy transfers of tiles to CRM are possible
  • A pool of present responses, conversation scripts, and templates that are ready for sending are all available

Here are some screenshots of what it looks like when you’re using it:

CRMUG CRM Summit Takeaways


Ledgeview CRMUG


Ledgeview CRMUG


2. Maplytics
Maplytics is a mapping tool developed by Inogic Technology. The company is based out of India and offers additional products outside of its mapping program.

Key features of this new technology include:

  • Easy integration with Microsoft Dynamics 365 Solutions
  • Mobile usage is available
  • Results on the map are based on CRM Security Roles
  • Users have the ability to map up to three entities on the map at one time
  • Users have the ability to “union” data on the map to report on information in a set area
  • Location-aware appointment scheduling and route planning are available to users
  • Territory management and re-alignment is made easier
  • Can use CRM data based on mapping for Marketing Automation Campaigns
  • Geo-Analytics Dashboards are available to users
  • Heat maps are available to users

Ledgeview CRMUG


We hope to see you at next year’s #UserGroupSummit in Orlando, FL! We’re positive it will be another great event for the Dynamics Community.

If you want to learn more about what it takes to be a Microsoft Dynamics 365/CRM User or Admin powerhouse, join us for our next Microsoft Dynamics 365/CRM User Group Webinar.

Register here.

Microsoft Dynamics 365 CRM User Group Webinar

Setting Up Microsoft Dynamics Portal Administrator Access

$
0
0
So, you’ve installed a portal, nice work! Now you want to get logged in and start editing things. The easiest way is via the portal itself rather than from CRM. So how on earth can you do that? You...(read more)

Get the logged in users Dynamics user record ID in a Canvas PowerApp

$
0
0
When working with a canvas PowerApp that integrates into Dynamics 365, you occasionally need the current users' Dynamics user GUID. This could be used to populate lookup references on the various records...(read more)

Tip #1186: Race conditions with queue items

$
0
0

Today’s tip is from Marius “flow like a river” Lind. (And you can also become a tipster by sending your tip to jar@crmtipoftheday.com)

What happens when a race condition happens in a queue? Let’s say we have a bunch of customer service representatives who are working on cases in the same queue. The queue is sorted by priority and you should always pick the top case. Joel and Marius opens up the queue view at the same time, but Marius is a second faster than Joel to pick the top case. What happens now?

Well, one out of two things.

  1. Marius chose to pick but not remove the item from the queue.
    Joel picks the case, and since the queue item still exists the action taken by him simply resolves and the case is delegated to him.
  2. Marius chose to pick and remove the item from the queue.
    Joel is presented with the following error message
    clip_image002

So how do we deal with this?

For scenario 1, here’s a few options:

  • Accept that this might happen
  • Create a plugin which prevents someone from picking something that’s being worked on

For scenario 2:

  • Tell users about this, accept that it might happen

How to reduce the risk of this happening:

  • Make sure you teach your users to refresh the list view if it’s been open for a while
  • Distribute over several queues to prevent too many people working in the same queue
  • Or maybe you have a better idea, drop it into the comment.

Best regards, your friendly neighbourhood Viking!

(Facebook and Twitter cover photo by davide ragusa on Unsplash)

Dynamics 365 Error Adding Product Bundles After Upgrade to Version 9

$
0
0

After doing a test upgrade of an 8.2 instance to Version 9, we received an error when adding product bundles to an opportunity where the bundle had existed in 8.2. When adding a bundle from the grid it would return an error with the code - 2147206380.

image And from the Opportunity Product form it would return a Plugin error with the message ‘The specified unit is not valid for this product’.

image

This did not affect new product bundles that we created in Version 9, even if they were identical to the existing bundles that could not be added.

We resolved this by updating the instance to version 1710 (9.0.2.1468).

The Field Service Sessions

$
0
0
For the next few months i will be dipping into the world of Field Service and bringing everyone some how to videos on everything from installing FS in your instance to filtering RMA Products by Purchase...(read more)

SiteMapName in the AppModuleSiteMap is null or empty error while importing V9 Solution in Dynamics 365 Customer Engagement

$
0
0
We recently upgraded our Dev and Test environment to V 9.0. Dev Test While importing a solution from Dev to Test which had SiteMap we got the below issue. “The SiteMapName in the AppModuleSiteMap...(read more)

How to Use CRM Campaigns to Prove Your Worth as a Marketer

$
0
0

I’ll let you in on a secret: in most organizations, marketing is a cost center. We’re the department of spending money. The department of pretty pictures and “branding” campaigns. The department where budget goes to disappear.

 

The good news is we can beat that perception by better putting to use the CRM Campaigns entity—all it takes is a little strategic thinking and some calculations of the data you already have available to you inside Dynamics. Here’s how to prove your worth as a marketer by using the Campaigns entity:

 

First, the Basics

“Campaign” can have a different meaning in the context of marketing than what you might find in the context of your CRM. In marketing, a campaign is a series of activities organized to work toward a particular goal, like sales. In the context of your CRM, a Campaign is a record that gives you a place to keep track of activities, costs, responses, and potential ROI of marketing spend.

 

There are occasions in CRM where a Campaign will not fit the standard definition of a marketing campaign—but we’ll get to that a bit later.

 

For the purpose of this post, we’ll focus on the CRM definition of Campaign. In Dynamics, this could be one of two types: either a Campaign or a Quick Campaign.

 

The differences are as follows:

 

A Quick Campaign is a great way to run a one-time offer or a flash sale, but if you’re looking for long-term tracking of a marketing activity (i.e., something you’d want to track an ROI to), your best bet is to create a Campaign.

 

With each new Campaign you build, you’ll want to add the following pieces of information (at a minimum):

  • Name
  • Actual Start/End
  • Estimated Revenue
  • Marketing Lists
  • Campaign Activities (for tracking true cost)
  • Offer
  • Allocated Budget

 

We’ll get to gathering that information a bit later, but keep in mind these fields will help you keep track of your marketing successes in the long run. Plan on needing that information as you move forward.

 

The Architecture

Now that you’re oriented in the Campaigns Entity, you can create the architecture for your success. Dynamics has two layers of tracking available out of the box:

  • Lead Source (an option set)
  • Source Campaign (a pick list that pulls from new campaigns created in the Campaigns Entity)

 

Think of Lead Source as your big bucket—this is where you track the success of marketing activities as a category, like Events, Trade Shows, Paid Search, or Website Lead. This layer of tracking will help you understand what types of marketing events are performing well for your company.

 

Think of Source Campaign as your little bucket—here’s where you’re digging in at the campaign level to determine if a specific trade show or a specific paid search campaign was worth the investment. Your measurement here is the ROI on a specific campaign. This layer of reporting is great for you to know as you plan your next marketing budget, but it probably isn’t the type of report you would take to a financials meeting.

 

Once you select your Lead Source categories, be sure to map them to the appropriate Source Campaigns or campaign types. You’ll want to share this information with your sales team, like so:

 

Start Your Marketing Plan

You should have a marketing plan before you get your hands into the Campaigns entity. But getting this plan together will involve a dive into what’s happened historically on the Lead and Opportunity side of your CRM. In order to get the numbers you’ll need to prove your worth, you need to know the following:

  • What’s your Lead to Opportunity conversion rate?
  • What’s your Opportunity to Closed/Won rate?
  • What’s your average deal size? Per product/service?
  • What worked last year (e.g., where did your sales come from)?
  • What do you want to try this year, and how much do you think it will cost?

 

This exercise does two things—first, you can set expectations for your leadership, yourself, and your sales team, and second, you can give yourself some baseline numbers to track your success. You might put these numbers into an Excel spreadsheet, where each Lead Source is a table and each row is a Source Campaign, like so:

In the Campaign entity, these numbers will be reflected in:

  • Estimated Revenue
  • Expected Response
  • Budget ROI

 

This exercise is also useful for showing your sales team what success looks like from each event (how many Leads do we need? How many Opportunities do we need?) and for determining if the response you need to get your target ROI on an event is even possible.

 

Put Those Campaigns to Work!

Once you’ve built your budget, upload each row in your spreadsheet as a Source Campaign, along with the appropriate numbers from above. Keep in mind you will likely want to track additional sources that are not ROI-oriented, and that’s okay.

 

You can create perennial campaigns, like Referral, that don’t have an associated cost or projected ROI. All you’re trying to do here is figure out where your successes come from, and sometimes those successes aren’t from a true marketing campaign.

 

Proving Your Worth

You’ve got data—now you need reports. Think of your Little Buckets—your Source Campaigns—as what Marketing cares about, and your Lead Sources as what the executive team cares about, and create reports accordingly. You’ll need to know what’s working at the campaign level as you build out your budget proposal, but you can report to your executive team on the overall success of events as a strategy, or memberships as a strategy, and so on.

 

You can also use the numbers in your spreadsheet to set KPIs for your Marketing Department—how many total leads were driven in by Marketing last year, based on Source Campaign? That’s your starting point for creating a goal for this year. Similarly, how many Closed as Won Opportunities came from a Source Campaign that was a marketing activity? You now know what Marketing’s contribution to the sales pipeline is.

 

These are numbers that transform the Marketing Department from a cost center into a ROI-tracking machine—all the while proving the worth of the activities you’re running.

 

Want to see the calculations behind that sample budget spreadsheet? Ping me on LinkedIn with your email address, and I will send a sample sheet your way. You can also learn more about how to better talk to your CRM admins by reading this post here.

 

Natalie Jackson is the Marketing Director at emfluence and a resident CRM + Marketing Automation Software geek.

The post How to Use CRM Campaigns to Prove Your Worth as a Marketer appeared first on CRM Software Blog | Dynamics 365.

Viewing all 13977 articles
Browse latest View live




Latest Images