MSCRM 4.0 Developer Errors: My new pet hate
Published on Estimated reading time: 1 minutes
So if you follow all the posts on this site, you’ll know that I’m 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 separated most of the functions so that each customer is separated nicely, there are a few that aren’t. Developer errors are one of those: if you enable them, you enable them for all customers.
As a hosting provider, I do not want to have to enable them globally—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 them on and off all the time.