Robert MacLean
4 June 2008
So if you follow all the posts on this site you'll know that I am involved with a hosted MSCRM system. This is a great system as it allows multiple customers to share a single deployment, and while it has seperated most of the functions so that each customer is seperated nicely there are a few that are not. Developer errors are one of those, if you enable them, you enable them for all customers.
As a hosting providing I do not want to have to enable it globally as it means that the user interface for an error is ugly and I do not want to have to take individual support calls for customers to turn it on and off all the time.
As a hosting providing I do not want to have to enable it globally as it means that the user interface for an error is ugly and I do not want to have to take individual support calls for customers to turn it on and off all the time.