Hi FMcFaul, This is a known issue in Reporting Services 2005, and it is fixed for the next version of Reporting Services 2008 (Katmai). The issue is caused because the Auto derivation the XMLDP: When there is an empty value for the 1st row, the column is not displayed. To get it around, specify all the columns explicitly, for example, (@Column1,@Column2,@Column3,@Column4,@column5,@column6,@column7): <Query> <Method Namespace="http://schemas.microsoft.com/sharepoint/soap/" Name="GetListItems"> <Parameters> <Parameter Name="listName"> <DefaultValue>SomeListName</DefaultValue> </Parameter> <Parameter Name="viewName"> <DefaultValue>{d99b0402-38b9-48a5-87e9-2c6bf198a30c}</DefaultValue> </Parameter> </Parameters> </Method> <ElementPath IgnoreNamespaces="true">GetListItemsResponse/GetListItemsResult/listitems/data/row{@Column1,@Column2,@Column3,@Column4,@column5,@column6,@column7}</ElementPath> <SoapAction>http://schemas.microsoft.com/sharepoint/soap/GetListItems</SoapAction> </Query> See http://blogs.msdn.com/b/mariae/archive/2007/12/13/querying-sharepoint-list-from-reporting-services-returns-only-not-null-columns.aspx for the detailed information about this issue. Check this thread http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/8f3d1d84-3bbd-4592-a51f-7301698918cf for the similar issue. thanks, Jerry

I recently started creating SSRS 2005 reports against WSS 3.0 SP1 lists using an XML data source. I've found that if a value of a field in the first row is NULL that entire field for every row is dropped. When the report is previewed, no values show up for that field in any row. If the value in the first row is not NULL, data shows up even if subsquent rows have NULL values. If the fields are refreshed in the data tab these fields drop out and the report encounters errors when previewing. Other than requesting a default value for a field (which I don't have any control over) is there an alternative method for ensuring that the field doesn't get dropped once the data is brought over to SSRS? Does this occur in other versions of SSRS or SharePoint?