Welcome to my knowledgebase, which contains snippets of information that I find (mostly about Microsoft Dynamics 365/CRM) and then forget.
You are most welcome to browse and if any of the information helps you in your work with Microsoft Dynamics CRM then that is great.
Use the search box or the tag links to search for articles.
I’m an experienced Microsoft Dynamics 365/CRM Consultant and Microsoft Certified Trainer available for hire on an ad-hoc basis. Please contact me to see how I can help with your Microsoft Dynamics project. Find out more about me.
Recently updated articles
25 May 2016
I encountered an error with the CRM 2011 Client for Outlook when running on Office 2016. The error is about webformhost failing.
Although CRM 2011 is compatible with Office 2016 according to the compatibility matrix, it seems that several people have this issue.
The resolution that worked for me was to add a registry key as follows:
HKEY_CURRENT_USER > Software > Microsoft >MSCRMClient > UseWebFormProcessIsolation'
Use a DWORD32 key type and set the value to 0.
21 Mar 2016
Here are some reporting and data visualization tools:
- SQL Server Reporting Services
- Power BI (Office 365 service) and Power BI Desktop (report authoring tool) (but only works with CRM Online)
- Power Query for Excel (but only works with CRM Online)
- ZAP for CRM
- Crystal Reports
13 Mar 2016
Occasionally I'm asked by clients to provide a facility to mark records (usually contacts) as confidential.
I then have to establish what the client means by confidential. Most times, the client wants to have records that are marked as confidential visible only to a defined set of users even though the general policy is that all records are visible to everyone. However, there are other variations on what is meant by confidential. Staying with contacts the scenarios I've encountered include:
18 Feb 2016
UPDATE - Behaviour has changed
I retested the scenario below in CRM 2016 and the behaviour is now different. To summarize the behaviour in CRM 2016:
24 Jan 2016
Some companies keep tight control on which accounts can be a member of the sysadmin fixed server role in SQL Server. When installing CRM, although the installing user does not need to be a domain admin, the user does need to have certain administrativwe rights and this includes being a member of the sysadmin role on the SQL Server as per this article https://technet.microsoft.com/en-us/library/hh699825.aspx under the section Microsoft Dynamics CRM Server setup.