On Friday, September 14, we have released our latest version of the CRM to Exchange Synchronization application. The latest release, now also available for a 30-day trial, includes additional new features as well as easier configuration, multi-culture support logging capabilities and more.
Many times we are required to have a process or task that will automatically execute at a predefined interval (such as every first of the month), but Microsoft Dynamics CRM does not have a built-in engine to have such a process. An example of this would be updating the Month-To-Date totals of a particular entity.
Visual Studio 2010 and Report Builder 3.0 RDL reports use a new schema that is not supported by SQL Server 2008 Reporting Services. They are designed to work only with SSRS 2008 R2. Currently there is no way to publish a VS2010 Report on SQL Server 2008 without some modifications to the RDL code.
Sometimes, just as we would have a Navigation link that displays an IFRAME, we would like to display a View from another entity in there.
Integrating Google Maps or Bing Maps with Microsoft Dynamics CRM is a requirement that we often come across.
This blog will demonstrate how to add a new button to the CRM account entity and when clicked it will display the map of the address in a new browser window.
The System.Management.Automation assembly allows the exeuction of Powershell commands against Exchange server.
Although, it would seem that the same code would be able to run for both of the versions of Exchange Server, two different codebases are required. The reason for this is that Exchange 2007 (SP1) supports only local Powershell, and Exchange 2010 uses remote Powershell.
When using SQL Server logins to connect to a database that has just been restored, most likely the following error will appear: Login failed for User ‘username’
