Active Directory Products
Calls To Calendar
SMS To CSV
SMS To Gmail
Voicemail To Gmail
How Long For Me
My Music To Me
<< Back To All Blogs
Retrieving data from SharePoint SOAP Requests using LINQ
Wednesday, May 13th, 2009
As I have been doing quite a bit of work with the SharePoint web services I recently came across an interesting issue related to querying SOAP XML, and specifically in SharePoint. This issue also applies to other SOAP requests, and XML requests in general that have Namespace prefixes.
The issue arises while trying to do a very common LINQ query such as the following:
var lists = from list in doc.Descendants("List")
Description = list.Attribute("Description").Value,
Id = list.Attribute("ID").Value,
Title = list.Attribute("Title").Value
I was positive that my query was correct, but it was continually returning 0 results.
Enter the world of namespacing. I assumed that because the List element was not specifically prefixed that it would not matter, but I was wrong.
From a few levels above, in this example the element was GetListCollectionResponse, there was a namespace declared which was http://schemas.microsoft.com/sharepoint/soap/.
You cannot simply add the namespace with a colon in LINQ because it is an invalid element name.
You need to declare a specific XMLNamespace element like so:
XNamespace s = "http://schemas.microsoft.com/sharepoint/soap/";
Then, modify the above query to change the doc.Descendants element to the following:
doc.Descendants(s + "List")
After this minor modification everything worked exactly as expected.
Namespacin' Tom Out.
Fixing 400 RequestLength Issue in SharePoint and IIS
Retrieving User Name and MetaData through WCF Web Services for SharePoint 2010
Fixing "The given key was not present in the dictionary" error in SharePoint 2010 Installation
Reading Digital Signatures from InfoPath Forms in MOSS 2007 and WSS 3.0 Workflow
What causes "Please wait while scripts are loaded..." in SharePoint
Currently no comments.
Add A Comment
Email Address: (not public, used to send notifications on further comments)
Enter the text above, except for the 1st and last character: