- Improve error messages from web service API
- Posted by David Yack on August 6th, 2006
The CRM Web Services are great, but the error reporting could certainly be
improved. The following is an example of an error I received back simply by
misspelling the name.
Hmm…If they knew the specified name didn’t exist, couldn’t they tell me the
name of the attribute? Don’t get me wrong I’m all for hunting for the needle
in the hay stack, but let’s save it for when we really don’t know the name!
<detail><error> <code>0x80041103</code> <description>The specified attribute
does not exist on this entity.</description> <type>Platform</type>
</error></detail>
The errors from web services should provide as much information as possible
to help the caller resolve the problem.
--
David Yack
MVP / Microsoft Regional Director
Main Blog: http://blog.davidyack.com
CRM Blog: http://crm.davidyack.com
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/Businesssol...oft.public.crm
- Posted by Computroll on July 3rd, 2007
The error handling for the CRM webservices is terrible. I have been creating
a custom membership and role provider for an ASP.NET web application using
the webservices and it has been extremely difficult to make any significant
progress due to the poor error handling. I too have been getting the dreaded
error:
<detail><error> <code>0x80041103</code> <description>The specified attribute
does not exist on this entity.</description> <type>Platform</type>
</error></detail>
But instead of telling me which attibute it is breaking on I have to check
all entities and attributes used in my query. Hopefully I will not get fired
for drinking on the job, because I need a beer right about now...
- Posted by Jeffry van de Vuurst on July 3rd, 2007
Before you get a beer, turn on CRM tracing
. That's where you can find the
detailed error message, including which attribute causes the problem.
BTW, I totally agree that the error messages have a lot to be desired.
--
Jeffry van de Vuurst
CWR Mobility BV
http://www.cwrmobility.com/weblog
--
"Computroll" <Computroll@discussions.microsoft.com> wrote in message
news
7E07F9F-0240-490B-B804-296991E11488@microsoft.com...
- Posted by Michael Höhne on July 3rd, 2007
Yep! See http://www.stunnware.com/crm2/topic.aspx?id=ErrorInfo and
http://www.stunnware.com/crm2/topic....TraceLogViewer.
--
Michael Höhne, Microsoft Dynamics CRM MVP
Web: http://www.stunnware.com/crm2
Feed: http://www.stunnware.com/crm2/atom.aspx
Custom Lookup Dialog: http://www.stunnware.com/crm2/?area=customLookup
The JavaScript Snippets Directory:
http://www.stunnware.com/crm2/topic.aspx?id=JS13
----------------------------------------------------------
"Jeffry van de Vuurst" <reply.to@newsgroup> schrieb im Newsbeitrag
news:019A3919-C2CD-414F-9860-CE37FD874D25@microsoft.com...