Article ID: 2826162 - View products that this article applies to.
Consider the following scenario:
For example, you create a new view in SharePoint in which you select the Show all items without folders view option in a Document Library. You set the new view as the default view for the document library. In this situation, the report returns different data in the SharePoint farm than in the report designer.
Note If you deploy the report to the SharePoint site, only the top level folders and files of the Document Library are returned. However, the report designer returns all files that reflect the default view change regardless of folder locations.
This issue occurs because of different code paths that are taken by SSRS 2008 R2 or SSRS 2012 when SharePoint runs the report in the same farm as the list. When the local SharePoint farm runs the report, the list is retrieved by using the SPLocalConnection path. The path reads directly from the SharePoint list without SOAP calls and builds a local copy of the list information without the default view configuration. Therefore, the SPLocalConnection path does not reflect changes in the default view.
However, when the report designer runs the report, the report uses the SPRemoteConnection path. This path uses SOAP calls that resemble the GetListCollection
(http://msdn.microsoft.com/en-us/library/lists.lists.getlistcollection(v=office.12).aspx)function. This function accesses the site through a remote HTTP connection instead of the local connection. Therefore, changes will be reflected in the default view configuration.
To work around this issue, use one of the following methods:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2826162 - Last Review: March 19, 2013 - Revision: 1.0
Contact us for more help
Connect with Answer Desk for expert help.