Tag Info

Hot answers tagged

4

Cross-Page connections are only supported by a few old webparts as it became obsolete after SharePoint 2003. In order to support Cross-Page connection the web part need to: derive from the Microsoft.SharePoint.WebPartPages.WebPart instead of System.Web.UI.WebControls.WebParts.WebPart (the recommended approach since WSS2.0/MOSS2007) declare the interface ...


3

SSRS, to be used in SharePoint Integrated Mode, must be installed on a server that has SharePoint installed and joined to the farm. Obviously this would not be a good idea to install SharePoint on a Database Engine server if you can avoid it. Install SSRS on your SharePoint server in Integrated mode. Yes, you must license SQL Server (SSRS) on your ...


3

In the Expressions dialog box of your report builder you can use the global variable UserId. Alternative, create a custom webpart which renders an Iframe (URL = reportviewerpage). Pass the current user data as a querystring. Use the querystring value (report parameter) in your report query.


3

You need to install Reporting Services Shared Addin in the SERVER 2 [your second WFE]. Kindly refer to the scale out architecture mentioned in technet. http://technet.microsoft.com/en-us/library/hh479775.aspx The presentation layer of SSRS reports on SharePoint Integrated mode depends on this component which adds specific capabilities on Web Servers to ...


3

The RSViewerPage.aspx is a Out the boxed application page in the _Layouts folder. Application pages, which are also known as "_layouts" pages, are stored in a site's Microsoft Internet Information Services (IIS) virtual directory and support application implementations. Application pages are shared across all sites on the server, whereas a site ...


3

Use the Globals!ReportServerUrl variable from within Report Builder: If you just want the base URL of the site, then remove the _vti_bin bit by using an expression: =Replace(Globals!ReportServerUrl,"/_vti_bin/ReportServer","")


2

One workaround is to look at the structure of your pages. Consider what information your user requires on each page. If some information is almost never used place it on a separate page. That way you will be able to give the users most information they need reasonably quickly, while requiring an extra request for information that is not used as often.


2

There are a number of variables that go into a decision like this. I would probably start with a Data View Web Part (DVWP). Can you explain more about what type of reports you want? UPDATE 2010-04-21: Based on the additional information you posted above, I'd probably still stick with the DVWP suggestion. If the number of values [X, Y, Z] are fixed, then ...


2

Either use the methods in this link to turn on error messages, or you should be able to log on to the physical server to see the detailed error messages.


2

I've been dealing with this issue for a couple of months now and finally was able to resolve it. In my situation it was because I was using the same hostname for my reporting services URL and my SharePoint site URL. My environment looked something like this: SharePoint site for reports: http://mysphost/reporting Reporting Service Integrated Mode URL: ...


2

Needing to review and approve content is precisely one of SharePoint's core use-cases, so that requirement is definitely not an issue :) I would have the reports sent to separate Document Libraries, with permissions set up so only the relevant people can view them. Set up Content Approval on those libraries, so when they are added, they need to be viewed ...


2

Enable auditing in the Site Settings of your site collection and you can use the reports generated by SharePoint to track user activity. However, that is limited to only what they access within that SharePoint site collection and would definitely not track external links. If auditing is not enabled now, then it is also limited only to future actions. If ...


2

The 504 Gateway Timeout error is usually a network error between servers on the network or an issue with an actual server. This may also mean that the report server is down or not working properly. If you have manually configured the proxy , verify that Bypass proxy servers for local addresses is set to true. <system.net> <defaultProxy> ...


2

That's right, SSRS "Business Intelligence Development Studio" (or BIDS) project files won't work with the Visual Studio 2010 shell. But there is no reason you cannot simply use the Visual Studio 2008 shell, which is what the SQL Server client tools should be installing for you. Just be sure you install the SQL Server Client Tools into the DEV environment, ...


2

Ended up solving this myself using Powershell instead of C# (using mock-variables in this snippet). The Powershell script must be executed from the SharePoint server and under administrator privileges (both windows & SharePoint I believe). Edit: Also note that my SiteCollection is the root web for the web application #Powershell Clear-Host # Add ...


2

We were able to get the RS component to successfully install by extracting the RSSharePoint.msi package from the SQL 2012 SP1 redistributable and using msiexec manually to install the package on each of the servers. The SSRS instance was unchanged, and once we had the SP1 SSRS SharePoint component installed on each of the WFEs, it worked fine - I'm assuming ...


2

It doesnt matter. However you must install the reporting services addon for SharePoint on the WFE (Front-End Server) if you want to use the "SharePoint integrated mode". You can find more infos here


2

See the post history for my previous version of this answer, it's actually wrong. SSRS 2012 as a service application is the equivalent of the Add-In in 2010. You can probably install and license in exactly the same way as before, but you install the SErvice Application where you previously installed the Add-In.


2

You're correct in that it needs access to the object model when running in Integrated Mode. In Native Mode the reports run in SSRS/SQL and not SharePoint directly. The report viewer for a native mode report is just an iframe, essentially. In integrated mode the reports are stored within SharePoint, so SSRS needs to be able to communicate with SharePoint to ...


2

Use Report View webpart, Add the Report Viewer Web Part to a Web Page (Reporting Services in SharePoint Integrated Mode) You can set webpart's property Show refresh button to true, so when a user clicks on refresh button it will update report.


1

Check the permissions of the Report Library where the reports(.rdl) are uploaded. At times,report library will need contribute level access rights for all the users who wish to see the reports inside this library. Also it is advised that do not use inherited permissions on the report library. Stop inheriting permissions and give permissions directly on the ...


1

I haven't tried it but would probably prefer to use the XML Data Source and the REST api accessing http://site/_vti_bin/listdata.svc/listName?$select=Title,BusinessUnit,ScanDateTime&$filter=(ScanDateTime lt datetime'2012-04-10T00:00:00') and (ScanDateTime gt datetime'2012-03-01T00:00:00')


1

Finally found the actual cause after I closely followed this link: http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/daa59eec-b651-42dd-9f6c-42aaa3fa4523 Looks like the original account that was used to create the *.rdl files and the data connection library was removed from SharePoint. The resolution is download the rdl files and ...


1

Here you have fully functional PS script: Add-PsSnapin Microsoft.SharePoint.PowerShell $siteUrl = "http://mycoolsite" $web = Get-SPWeb $siteUrl @(foreach ($group in $web.SiteGroups) { foreach($user in $group.Users) { $usergroup = New-Object System.Object $usergroup | Add-Member -type NoteProperty -name GroupName -value $group.Name $usergroup ...


1

You could create a console application for SharePoint. in VS2010 An example for all groups would be: using (SPSite site = new SPSite("http://yoursiteurl")) { using(SPWeb web = site.OpenWeb()) { foreach(SPGroup grp in web.SiteGroups) { foreach(SPUser usr in grp.Users) { string sGroupName = grp.Name; string sLogin = ...


1

I just re-read you question and assuming I understand what you're trying to do I don't think you'll be able to do what you want to do with a CAML query. It sounds like you want to return a result that contains a row for each user based on the last (MAX) date of one of the colums in the list. You'd need to do an OrderBy on the date column and a GroupBy on ...


1

Finally I resolved the issue by verify the services account that using in the reporting server which integrate with SharePoint Server. The services account delegate to the particular server that not part of reporting server. When remove the delegation for this services account in the AD. It solved my problem. This required to using Kerberos Tracking method ...


1

With advance reports performance is major concern, I will go with Performance Point its very powerful but you can only build KPI by selecting Sharepoint List as data source, when you want advance charts you have to build SSAS cubes, but you cannot directly build SSAS cube on top sharepoint as sharepoint is not a relational database, so you will end up doing ...


1

Powerpivot worked well for a Executive Portal I developed. Consider that solution. For the right problem, it is one hellava solution. Agree with James Love about PPS. Disagree with Michael about Enesys. Enesys data connection to Infopath library did not fulfill the intended need. May work well for basic lists, though. Watch out for the rendering delays of ...


1

PerformancePoint without any other data sources is very limited. If you have a SharePoint environment, find out if you can have access to an instance of SSAS on the SQL Server. You'll then be able to either locate a cube you have access to, or copy over the AdventureWorks SSAS database. PerformancePoint comes to life when you have analytical data sources ...



Only top voted, non community-wiki answers of a minimum length are eligible