Sonoma Partners Microsoft CRM and Blog

Introducing Dynabacus – Microsoft CRM Record Count Tool

Today’s guest blogger is Mike Dearing, a Principal Developer at Sonoma Partners.

Ever wanted to get an accurate record count of all of your organization’s companies, contacts, <enter additional entity names here…>?  Well, you aren’t alone.  Your current options to accomplish this are limited. They include doing excel exports, writing reports, or performing SQL count queries (if your deployment is on-premise). We decided to develop a user-friendly, managed solution that you can easily drop into any Dynamics 2015 on-premise or online environment to perform these counts for you.  Dynabacus (the Dynamics-abacus) gives CRM administrators the ability to get the record count of any number of entities (native or custom) simultaneously.  Administrators can also refine these counts further by applying personal and system views if they choose to do so.  Then with the simple click of a button, Dynabacus crunches the numbers for you using supported API calls and returns the results.


And the best part is, it’s available now for free! Download it today and let us know what you think!

Topics: Microsoft Dynamics CRM 2015 Microsoft Dynamics CRM Online

Announcing CRM DevTools for CRM 2015 and Update 1!

Last January we released a brand new tool called CRM DevTools for CRM 2013 and 2011 UR12+.  Today we’re happy to announce a new update that supports CRM 2015 and CRM 2015 Update 1.  If you missed the original release, head here for usage information or here for the latest release.

Along with CRM 2015 and Update 1 support, we added a few more handy features.

Note:  Most of these new features will open a new window so be sure enable pop-ups

Form Tab – Record Properties

The Record Properties button on the Form tab brings back the old Properties page from CRM 2011 that still exists but isn’t surfaced anywhere in the UI.  The page displays the permissions on the record and the Created By, Created On, Last Modified By, and Last Modified On.



Form Tab – Performance Center

The Performance Center button on the Form tab displays the native Performance Center on top of the record form.  The Performance Center is used to debug any performance issues with a record form to see where it can be optimized.



Debug Tab

The new Debug tab replaces the old DB & Server tab.  The information from the old tab is now within the Environment Info button.  The Debug tab has 5 buttons to provide easy access to native debug pages within your CRM environment.


Debug Tab – Diagnostics Page

The Diagnostics Page button opens the native Diagnostics page for your environment.  This page helps debug any network issues and admins can use it to run a latency and bandwidth test.


Debug Tab – Environment Info

The Environment Info button opens the native Debug Information page for the CRM environment.  It contains version information for the CRM server and database, along with other settings. 


Debug Tab – Default Solution

The Default Solution button is pretty straight-forward and will open up the default solution for the organization.

Debug Tab – CRM For Tablets

The CRM For Tablets button will open up the CRM For Tablets app within your browser.  This is very handy to help debug any JavaScript issues with the app.  The native browser developer tools can be used to see any JavaScript errors that might occur within the app.  It can also be used to just see how the app will look with your organization.


We hope you enjoy the latest release of CRM DevTools as much as we do!  Hit us up in the comments with any feedback or suggestions for future releases.

Topics: Microsoft Dynamics CRM Microsoft Dynamics CRM 2015 Microsoft Dynamics CRM Online

Refreshed Dynamics CRM Phone App Available

A few months back, Microsoft announced the new and improved version of their Phone Client would be available with the Spring 2015 release.  However, with releasing any app to the various app stores, they’re not released immediately.

However, recently the app did show up in the Apple app store and we were able to get our hands on it to take a look and compare it to the previous version.  The previous version is still available in the app store, and has been rebranded “Dynamics CRM for phones express.”  A couple years ago we blogged about it’s release and the functionality it provided back then.  I linked to that post so you could compare and contrast the look and feel of the previous express version, to the new and improved version.

The new version, branded “Dynamics CRM for phones”, is now available in the Apple store, Windows store, and Android store.  You can tell the difference in the apps based on the icon and name.


Microsoft is moving to a “configure once, deploy everywhere model.”  What does that mean?  That means the life of a configurator is going to be that much better.  More specifically, the form customizations you make in the CRM web client, will now not only be what you see on the CRM Tablet client (as they have been since it’s release), but will also be what you see on the new CRM Phone client.  Therefore instead of having to update the main forms AND the mobile express forms, you’ll just need to update the main form for any changes you make to be applied across the board.

Now to the details.  What does the new Phone Client look like?  Well if you’ve used the Tablet Client before, it’ll look very similar to that.

When you initially log in (requiring only your IFD URL to your organization, user id and password), you’ll see your home page.  This home page is the Sales Dashboard.  However, in the Web Client, you can create additional dashboards that can be selected when you’re on the home page on the Phone Client, and you can also make that dashboard your default dashboard.

image  image

As you can see, from here you’re able to view records that you’ve pinned to your home page.  You can also resize tiles that are on your home page and this makes it super convenient for records with contact information like the Patrick Sands sample contact record above.  You can easily email and call this contact now directly from your home page without having to click into his record.

You can also see at the top of the page the global menu bar which has the following commands from left to right:

  • Back – takes you to previous pages
  • Home – takes you to your home page
  • Search – initiates a multi-entity search
  • Site Map – displays the entities you can navigate to

Also on all pages at the bottom right is an ellipses.  Clicking on this presents more options for the area you’re working in, as well as allows you to create a new record from anywhere you’re at within the application.


When you navigate to an entity from the site map, you can create a new record of that entity type by clicking the plus button at the top of the page.

image image

When on a record, you can view the data about the record and related data very easily.  The Phone Client now uses the same exact forms that the Tablet Client and Web Client use (configure once, deploy everywhere).  If you’re going in to talk to a customer, you can navigate to their account and view any open cases or opportunities immediately from the Phone Client.  You can click into an Opportunity to then see the process based form, and where you’re at within the sales process.

image image image

The phone app also allows you to easily create emails and make phone calls by clicking on email address and phone number fields.  The email fields will automatically open your native email client, and the phone fields will automatically initiate your phone client.  The good thing is after you hang up the call, you’re returned to CRM with a new phone form initiated so you can just punch in the details and click save.

image image

image image

The integration between the Phone Client and the native mobile phone doesn’t end there.  Any address field on the application is clickable, and when doing so, you’ll open up the native map application.

The Phone Client also has a disconnected mode just like the Tablet Client.  While the offline mode is better that previous versions, this is still lacking in that it’s not showing you all records that you have access to, but instead, recently accessed records.  You can create new records while offline (called offline drafts), but unfortunately you cannot modify records while offline unless it was one that you just created while offline.  You can view your offline draft records by navigating to them via the Site Map (you’ll see a new “Draft Records” entry with a count of drafts).  Then when you’re back online, you can go into this list of drafts, and re-save them for them to save to the CRM database.  Not ideal, but is much better than nothing, and I’m really looking forward to what Microsoft has in store for vNext.

image image image

It’s great to see Microsoft continue this “mobile first’ mode and add more products to it’s repertoire.  Enhancing the Mobile Express app and making a true mobile phone app now rounds out their suite of products (web, tablet, phone) to all be first class.  Next steps are to add more features to these apps so that functionality that’s available on the web, is also available on these apps (e.g., custom web resources).  I’m also looking forward to seeing how they further improve on their offline story, and hopeful they provide a true offline solution where users can work with existing records while offline, and not only new records they create while offline.

However, as you can see, the application is pretty robust as it stands.  And the best part is the cost:  FREE!  Go ahead and download your copy now and start playing around.

Topics: Enterprise Mobility Microsoft Dynamics CRM Microsoft Dynamics CRM 2015 Microsoft Dynamics CRM Online

You Too Can Snoop… But Not In A Creepy Way

Today’s guest blogger is Stephen Habegger, a Senior Developer at Sonoma Partners.

Awhile back, we showcased an application called CRM Snoop on our website. Snoop is a tool that allows developers to listen to Dynamics CRM plugin messages and peer into the darkest depths of an IPluginExecutionContext object. It’s a tool that can be extremely useful for plugin debugging and development and was only available for use internally at Sonoma Partners… until now.

We’ve recently revamped the application completely, moving away from its former incarnation as a WPF application and creating a new managed solution that can be installed in both on-premise and online Dynamics CRM 2015 environments. And now we’re making the solution publicly available here.

What’s In the Solution?

The Snoop solution will create two new entities in your Dynamics CRM organization, Snoop Session and Snoop Session Results. A Snoop Session represents a configuration for snooping on plugin messages (i.e. what entities and what messages you want to listen to). When you start recording a set of messages, a plugin is registered on those messages, and they are saved as Snoop Session Results records.

How Do I Use It?

After installing the CRMSnoop managed solution, navigate to Settings > Solutions. Click the new Snoop Sessions button in the command bar.


A new window will launch with a list of Snoop Session records. Open one or create a new one. When the form has loaded, select the entities and messages you wish to record. Optionally, select Include Available Images to register Pre and Post Entity Images where applicable. You can also select Only Record My Actions to ensure actions performed by other users don’t show up in your results. Then, just click Start Recording.


After you begin recording, the Results section of the Snoop Session form will display an animated timeline of messages as they happen. You can click on the message icons in the timeline or in the table below to display the detailed properties of the IPluginExecutionContext passed to the plugin message. When you are finished recording, click the Pause Recording button.



You can also navigate to the list of related Snoop Session Results in the header of the Snoop Session form. The form for an individual Snoop Session Results record also displays the results for that particular message.


It is important to note that the recording process relies on the Snoop Session record status. That means recording does not end automatically when the Snoop Session form is closed. The recording must be stopped by clicking the Pause Recording button. The recording may be resumed at any time with the same or altered configuration. In some scenarios it may make sense to let a recording continue over a period of time. However, we do not recommend this in a production environment as there may be a performance impact.

What Is It Good For?

Snoop is an excellent tool for developing and debugging plugins in a variety of scenarios. It allows the developer to see the input a plugin may receive without profiling or attaching a debugger. Use it to check out what fields are changing during an Update operation. Keep a link handy to a specific Snoop Session Results record for when you don’t remember what’s in that pesky Opportunity Won message. Record in a User Acceptance Testing environment to collect a log and figure out what those crazy users are doing to break your plugin.

Will you find another use for Snoop? Let us know what your favorite features are and how you use it.


Topics: Microsoft Dynamics CRM Microsoft Dynamics CRM 2015 Microsoft Dynamics CRM Online

CRM Online Spring 2015 – Alternate Keys

With the release of CRM Online Spring 2015 Update, Microsoft delivered the ability to define alternate keys for an entity.  Alternate keys can be one or many attributes that are a unique combination of columns to uniquely identify a record instead of using the typical primary key.  Alternate keys can be made up from a combination of decimal, integer or string attributes.

Lets dig into how the new alternate keys can work in CRM based on a real-world scenario.

In my example we have an entity for States and our Contact entity has a Lookup to the State entity.  The State entity has an attribute called Code where it will store the unique two character abbreviation for the State such as IL for Illinois.  There is an integration with another system where Contacts will be passed to Dynamics along with the two character abbreviation for State.  Alternate keys work perfectly in this scenario as we can just associate the State record to the Contact record by using the State’s Code instead of needing to query to find it’s GUID.

In order to accomplish this, we first need to go to the customizations for the State entity.  Underneath the entity is a new link for Keys.


Click New which will open a dialog and let you pick one or more keys that will make up a unique combination to identify a record.  We will select Code as a Key for our State entity.


Now with the SDK when updating a Contact record, in order the set a Lookup value we would need to use the EntityReference object and provide a GUID to a State record but with the latest Spring Update and the latest SDK, we can instead pass in a value for the Code attribute like shown in the snippet below.

Therefore if our integration sends us a Code for the Contact’s State such as “IL”, we can just update our Contact record using the “IL” value and avoid needing to do a query against the State entity to find the GUID for the IL State record.

One last thing to point out about alternate keys is that CRM will put a constraint on the entity to make sure the new alternate keys make up a unique identifier for the entity.  If you try creating a record with a duplicate set of alternate keys, you will see an error similar to the one shown below.


Topics: Microsoft Dynamics CRM Microsoft Dynamics CRM 2015 Microsoft Dynamics CRM Online

How to Mass Update Business Process Stages

Today's guest blogger is Rachel Sullivan, a Senior Consultant at Sonoma Partners

CRM allows you to easily update fields on records using their bulk edit functionality.  Records that you can query and return back in a list/grid can all be edited using this functionality.

However, since it’s currently not a field on the Opportunity form, there is no way to update the Business Process stage using this native bulk edit feature.  However, fear not, as Sonoma is here to provide a workaround on how to edit this field using native export/import.

In order to update the Business Process Stage using this workaround, follow these steps below.

1. You’ll first need to find the unique identifier of each process stage (the GUID).   To accomplish this, use Advanced Find to identify the opportunities that you would like to update.

3. Edit the columns and include Process Stage

4. Click Results and from this view, you can see all of the unique Process Stages and their GUIDS


You will need to match each unique GUID with the Process Stage Name.  The easiest way to do this is to open a record of each unique Process Stage value, view the Process Stage name.  Do this for each unique Process Stage.

For Example:

  • d3ca8878-8d7b-47b9-852d-fcd838790cfd = Propose
  • 650e06b4-789b-46c1-822b-0da76bedb1ed = Develop


5. Once all GUIDS are gathered, you’ll need to export the records that you’d like to update.  When doing this, make sure to check the box that makes the file available for re-import (note that with CRM 2015 Online Update 1, all records are automatically exported for reimport and this step isn’t necessary.  This should come to CRM 2015 On Prem in the fall).  Save the file locally and open it with Excel.


6. Once in Excel, copy and paste the GUID of the business process stage (that you’d like to change each record to) into the Process Stage column.  Save the file and import back into CRM.

Topics: Microsoft Dynamics CRM Microsoft Dynamics CRM 2011 Microsoft Dynamics CRM 2013 Microsoft Dynamics CRM 2015 Microsoft Dynamics CRM Online

Customer Success Story: Grant Thornton


"In our business, relationships matter." - Rick Stow

Grant Thornton LLP is one of the world's leading organizations of audit, tax and advisory firms. Although their revenue is in excess of $1.3 billion and they operate in 57 offices across the globe, Grant Thornton hasn't set out to be the biggest accounting organization in the world.

They know they compete with four larger firms, thus being the biggest doesn't differentiate them from the rest of the crowd. What does? Establishing closer relationships and personalized service that earns credibility and increases value. Enter the tool that helps Grant Thornton build and nurture personalized relationships with their clients: Microsoft Dynamics CRM.

Prior to their Dynamics CRM implementation, Grant Thornton lacked visibility into their contact and account records, as well as information that spanned across multiple employees and practice areas. Maintaining various customer management solutions, including SalesLogix, proved to be a challenge that sometimes led to duplication of effort and missed opportunities.


With one consolidated system, Grant Thornton is determined for their firm to maintain a meaningful relationship with each client in their CRM. Here are 3 ways their CRM solution helps them achieve this goal:

1. Commitment to Mobility 

A majority of Grant Thornton's employees spend a majority of their time outside the office, making the mobile component of their CRM project essential to their success. Not only did a mobile solution give their team members the functionality where and when they needed it, but it helped drive widespread user adoption - the key component of a successful CRM project.  

 2. Rise of Collaboration 

Relationships are everything in professional services firms, and people are very protective of their relationships and their contact records. Grant Thornton worked to overcome this mindset in order to understand the full scope of a client relationship. To foster effective collaboration, Grant Thornton integrated SharePoint, Lync and Yammer to promote a dialogue around client and account activities.

3. Enhanced Sales Processes 

Their new CRM solution accommodates different sales processes and regional requirements, helping to achieve the "One Firm" goal they had when starting the project. As collected data enters the CRM solution, employees can pinpoint the strengths, weaknesses, and threats of an opportunity. Because this information is centrally located and visible to appropriate parties - account managers can collaboratively develop a plan for pursuing the relationship. 

We worked with Grant Thornton for 11 months to create their custom Microsoft Dynamics CRM solution. Here are some lessons learned from their deployment: 


Don’t bite off more than you can chew. Your CRM project is ongoing and can be done in phases. It's okay to go live with fewer requirements and communicate broadly as you roll out additional functionalities. 

 Reduce the scope of the project: 

Don't go down the rabbit hole of adding on endless nice-to-have features. Most of your employees don't operate at that level of detail and if they do, they don't want to maintain a system that requires that much detail. Phase out the introduction of the system to drive widespread adoption.  

Are you ready to write your own CRM success story? We’re ready to help. 

Topics: CRM for Professional Services Microsoft Dynamics CRM Online

Always Look on the Bright Side of Your Data

Today’s post is courtesy of Ross Talbot, a Development Principal at Sonoma Partners.

In our continuing coverage of new features included in the CRM Online Spring 2015 Update, today we will be talking about optimistic concurrency.

First, a little review of data quality and minimizing data loss. Just as in life, there are two basic models for minimizing loss when updating data in your database: optimistic concurrency and pessimistic concurrency. Pessimistic concurrency uses row locks to prevent others from making changes while you are performing an update. This prevents a conflict by calling “dibs” and then releasing the lock when you are done. Optimistic concurrency involves an attempt to update and then a rollback if there is a conflict. This prevents a conflict by stopping the second update and letting the user know via an error message. Optimistic data tries first before stopping, and pessimistic data fights others off until its update is complete.

What does this mean for Dynamics CRM today? The lifeblood of your business starts with your customers, so from a CRM system perspective your customer data is vital. With integrations, mobile applications, and multiple users accessing and updating this data, you want to be sure that a situation that could potentially result in data loss is handled in a way that minimizes that potential issue. So let’s dive into an example of how these updates can be used in your code.

Before we start, optimistic concurrency is supported with this update on all out of the box entities enabled for offline sync as well as all custom entities. This is found as a metadata setting “IsOptimisticConcurrencyEnabled” and is set to true if the entity supports it. I have also set up a console app with some basic logging and an organization service to create a contact and test optimistic concurrency via an update and a delete.

Inside the app, I create Bob Brightside and then retrieve the record again so I can obtain the Row Version needed to check during our Update attempt.


From our log file, I see that Bob was created and that the current Row Version is 459773:
INFO "Contact Bob Brightside created with id: 24496e99-470a-e511-80d9-c4346bac7dac"
INFO "Row Version before update attempt: 459773"

Next, I use a breakpoint in my console app to simulate the timing of two updates. One will be made in my console app and the other in the browser. In my code, I will change the First Name field on the contact to Robert. I use the new ConcurrencyBehavior property to check the row version on my update. If the Row Version in CRM matches the Row Version of the contact record I am updating, the update will succeed. If these versions do not match, or if no Row Version is specified, the update will fail. I pause at the breakpoint in order to update the contact via the CRM web interface, changing the First Name field to Mr. replacing Bob.


When I resume my console app, the update request is executed and the update fails.


From our log file, we see that the concurrency check noticed another change had occurred and prevented our update:
ERROR "Concurrency Check Failed: The version of the existing record doesn't match the RowVersion property provided."

Next, I retrieve the record again to ensure I have the latest Row Version. Our log shows this has been updated: INFO "Row Version after update attempt: 459780"
I now execute a Delete Request with the updated contact and the ConcurrencyBehavior property set to IfRowVersionMatches, and since no other updates have been made this request succeeds.


Here is a link to the MSDN article detailing this new feature for more information about the supported entities, fault codes when concurrency checks throw an exception, and additional sample code.

Are you having any issues with your CRM deployment? Concerned that you aren’t doing enough to prevent data loss? Don’t grumble, give a whistle. We can help things turn out for the best.

Topics: Microsoft Dynamics CRM Microsoft Dynamics CRM Online

Avoid Form Script Errors with CRM Online 2015 Update 1

As many are aware, the Dynamics CRM Online 2015 Update 1 has been live for a bit of time now.  With it come a lot of shiny brand new features for everyone to play with, of which we’ve been blogging about on our site for a bit of time now.

However, with all great new toys, there are usually some pitfalls to be aware of and avoid.  And this release doesn’t fall short of that classification, as there is a potential headache that most customers and partners should be aware of and plan for.

Microsoft posted on their blog some good detail about some performance improvements that were made to form load times.  This is great as I’ve heard from multiple customers (and experienced) the slow loading forms that seem to have popped up when CRM 2013 released with its new UI scheme.

As seen in the image below, the new rendering forms of Dynamics CRM Online 2015 Update 1 drastically improve load times of forms.


From Microsoft’s blog post, you can see details of what they changed to get this improved performance.  However, with those changes comes the risk of unsupported scripts now failing.  Some examples of where scripts could fail are:

  • DOM manipulations
  • Accessing internal iFrame URLs
  • Accessing unsupported APIs
  • Other windows related assumptions

However, the good news is that there’s a plan in place that you should follow to resolve these issues.

  • First off, make sure that you test your environment thoroughly in a sandbox instance before updating your production instance to identify any potential issues.
  • If you find something that is broken, you can temporarily turn off the new form rendering by going to your System Settings, and setting the “Use legacy form rendering” option to Yes.  Note:  This option to use the legacy settings is most likely going away with the next major release, so please plan on fixing your broken scripts immediately to avoid issues in the near future.

  • You can also download the CRM 2015 Custom Code Validation Tool from this link, and run it on your environment to identify the usage of any deprecated API’s as well as any usage of unsupported API’s.

Moral of the story, be aware, be prepared, and have a plan.  You definitely don’t want to be caught by surprise in production when you’re getting random errors loading forms.  Good luck!

Topics: Microsoft Dynamics CRM Microsoft Dynamics CRM 2015 Microsoft Dynamics CRM Online

CRM Online Spring 2015 – Plug-In Trace Log

With the release of CRM Online Spring 2015 Update, Microsoft provided a long awaited feature for developers that we are really excited about.  That feature is a built-in Plug-In Trace Log that allows developers to utilize the existing ITracingService and provide a way to see any traces without requiring an error to occur to see the trace.

Here’s how it works:

  • First we need to enable the Plug-In Trace Log within the System Settings under the Customization tab.  You can choose to log only Exceptions or both Exceptions and Traces.


  • Next, utilize the ITracingService to write out a trace and/or throw an Exception within a plug-in


  • Next, register your plug-in on the desired step as normal.  In my example I am registering it on Create of an Account
  • When I attempt to Create an Account record then I receive an error message with the exception that I wrote in the plug-in


  • Now Navigate to the new link in Settings –> Plug-In Trace Log


  • You should see a grid of all the Plug-In Trace Logs per plug-in execution


  • Open up the trace record and you will see the details of any traces and exceptions that occurred with the plug-in.  It also provides the duration of the plug-in execution which will definitely come in handy for performance testing.


As you can see, this feature will come in handy and should eliminate the need to use a custom entity to store any log entries.  It also eliminates the need to require users to click the “Download Log” button on the error dialog in order to send the log file when an error occurs.

Topics: Microsoft Dynamics CRM Microsoft Dynamics CRM 2015 Microsoft Dynamics CRM Online