Every CRM developer knows the level of detail sometimes provided by CRM SoapExceptions. Sometimes the Details or InnerXML properties will reveal the actual error like “The specified object was not found.”, sometimes all we get is the infamous “Server was unable to process request”. These error messages are rather generic and can cause “mild” headaches, i’m sure you know what i’m talking about.
But fortunately the CRM MetadaService gives us opportunities to retrieve additional information about objects. Getting that information will produce some overhead, but it’s a good alternative to manually searching the CRM for exactly this kind of information.
Take a look at the following sample and the code below.
Continue reading →