Choosing the solution that’s right for your business is pretty important. But an equally important step for the success of your solution is choosing the implementation partner that’s right for you. Unfortunately, many businesses undervalue this phase of the decision-making process, and the results are not very pretty.
When trying to configure the CRM 2011 Outlook client I kept getting the error message, "There is a problem communicating with the Microsoft Dynamics CRM Server. The server might be unavailable. Try again later. If the problem persists, contact your administrator." However, Fiddler traces showed successful 200 responses from the Microsoft CRM Server and I was able to access the Microsoft CRM Server successfully from Internet Explorer.
You may have run into an issue with CRM Online 2013 after you have upgraded your CRM to the Spring 2014 Service Pack. The issue is that the Workplace tab gets removed. Microsoft is aware of this issue. If you experience the issue, you can contact them and they can fix the issue on the back end, thus giving you the Workplace tab back.
With the release of CRM 2013, there have been a bunch of new features that enhance user’s experience. One of the most powerful new features is the quick create option which allows someone to create another record rapidly from a view, or another form. Below is a screen shot from the view:
When a customer sends notification that they have acquired a new phone number or moved to another location, it can be a tedious task to update each employee’s details individually, especially when there are several contacts saved in Microsoft Dynamics CRM for the company.
This spring, Microsoft is releasing a truly significant enhancement to CRM. While there are a number of new features I could gush about, the one that I am truly excited about are the changes to the customer service module.
Recently I was working on a CRM 2013 Server installation for a customer who had a very well structured and stringent security model across their enterprise. Although we had followed the Microsoft documentation and Implementation Guide as well as providing our installation user the minimum permissions required, we were still seeing the following error: