SharePoint Designer is a handy application when you want to do quick modifications to your site. Like for example creating a data view web part. When you are working with XSLT and want to create your own templates, it is useful to know the returned SOAP message (XML output). This is something SharePoint Designer does not provide. To retrieve this information, you need to use another application called Fiddler.
With Fiddler you are able to log all the HTTP requests between your computer (SharePoint Designer) and the site you are working on.
As they describe it on their website:
Fiddler is a Web Debugging Proxy which logs all HTTP(S) traffic between your computer and the Internet. Fiddler allows you to inspect traffic, set breakpoints, and “fiddle” with incoming or outgoing data. Fiddler includes a powerful event-based scripting subsystem, and can be extended using any .NET language.
Download and install Fiddler to your computer.
Logging data to Fiddler
When you open Fiddler, you will get the following window.
Normally it will immediately start logging, so when you start SharePoint Designer and open a connection to your site, Fiddler will have logged all the traffic between SharePoint Designer and the site. If not, click File à Capture Traffic.
Now that Fiddler captures the traffic between SharePoint Designer and your SharePoint site, you can create a new page (if you already have one with a Data View Web Part on it, you can use it).
Insert an empty data view. You could also insert a list or library, but this will already have some custom styling. If you want to create your own, you should better start from an empty data view.
Click on Click here to select a data source and select the data source that you want to use. On the right side the Data Source Detail tab will open.
If you go back to Fiddler, new records should be available. When you are working with a Web Part page it will the following record.
If you do not know exactly which of the records is from the data source request, you could check the time and refresh the data source.
Select the record, and in the **Inspector **tab, select Raw output.
Normally you will get a notification that the message is encoded. This message could easily be decoded by clicking on the notification message: **Response is encoded and may need to be decoded before inspection. Click here to transform. **
After you clicked on the notification message, you will retrieve the decoded SOAP message (XML output).
Fiddler can be used for a lot more than retrieving SOAP messages, but for me this is very useful when I doing some XSLT styling.