Have you ever seen this little dialog while using Microsoft Dynamics CRM?
When you saw this dialog, did you click the “Send Error Report” button? If you have, thank you! You have helped make our product better just by clicking a button.
Andy Magee wrote a great post on how we collect errors and report them back to Microsoft. To supplement his post, I just wanted to let you know that we as a product team take these error reports very seriously. We want to build the most robust and reliable product possible and one way we do that is by addressing errors reported by Watson. (For more on Watson, check out this post.)
For example, as part of the UR7 release of Microsoft Dynamics CRM 4.0 for Microsoft Office Outlook, the Dynamics CRM team focused a lot of attention on fixing bugs that were reported by customers in this manner. This is one of the reasons why we feel our customers have been very pleased with the reliability improvements in the client.
Shifting focus to Microsoft Dynamics CRM 2011, we also leverage Watson during the development process prior to release. We have baked Watson error reporting into our automated tests. So if a test case runs and we see that an error was reported by Watson, we automatically fail the test case and file a high priority bug. Therefore, before we release any code, we have already identified and resolved many errors that would have been reported by customers. We think this is a very innovative approach that we have taken to Watson error reporting and one that really helps to ensure the highest quality product at release.
Of course, following the release, we still need customers and partners to let us know about errors that we may have missed during testing. So the next time you see the Send Error Report dialog, you can be assured that your error report isn’t being lost in the Internet ether. The product team is actively reviewing these error reports and fixing problems to make Dynamics CRM even better.