Globals!RenderingExtension in SSRS Reports in Local Mode - reporting-services

I am using SSRS Reports in loacl mode so i need to show them on a report viewer in a web project,
my problem is i want to hide some objects depend on its rendering Type Ex: Excel
But how do i do it because Globals!Rendering extension do not support in Local mode.
Any solution?

Pay for a third party's assemblies like GemBox to create a new Excel document from the returned byte[], then you can alter the worksheet however you want and add security.

Related

SSRS shared datasets missing

Source files for shared datasets are lost/missing. Any way to generate these from the SSRS report definition that is referencing them?
Thanks!
You can just download them from the server again.
Go to you SSRS home page (Report Manager, or Web Portal as its known in later versions of SSRS).
You might need to show hidden items, then open the datasets folder and you will see your shared datasets.
Click the one you need and there are options to either download the *.rsd file or open it directly in Report Builder, either way you will have *.rsd file which you can either add back into your Visual Studio project or open in a text editor and get the command text.

How to change ReportServerUrl in Report Builder 3.0?

We have 2 reporting server. One for test and one for production. Our business analyst will build the reports (rdl files) using Report Builder 3.0. After they complete the development and test on test reporting server (e.g. http://test/reportserver), we will modify the "ReportServerUrl" and Datasource, and then upload to production reporting server (e.g. http://prod/reportserver).
The problem is I cannot find in the Report Builder 3.0 UI how to configure this change. The only way I find is open the RDL file using Notepad, locate and then change the URL.
Since our analyst are not programmers I want to avoid use notepad. May I know where is the button to change ReportServerUrl?
Each time you add a Shared DataSource to a report or edit an existing DataSource (and therefore connect to a Report Server), the current report server is updated. This is shown in the bottom left of your Report Builder window ("Current report server...") and also gets written to the <rd:ReportServerUrl> tag in the .rdl file itself. This is just an indicator of the last Report Server which was connected to by the report.
Therefore, if you wish to change the <rd:ReportServerUrl>, you just need to amend the DataSource(s) in the report to be ones which reside on the Report Server whose URL you wish to have appear.

Adding SSRS report through CRM2016: Prefiltering doesn't work?

I've created a custom Reporting Services report from within Visual Studio that is intended to use automatic prefiltering as described here.
So, I've created my query as follows:
select fullname, createdbyname, createdon
from FilteredContact as CRMAF_FilteredContact
order by createdon desc
However, once I add a new Report in CRM based on the report's .rdl file (as described under "Deploying the Report" here) it adds the report fine, but two things happen:
1) The shared data source for this report is initally invalid, both CRM and SSRS refuse to render it with the error:
"The report server cannot process the report or shared dataset. The shared data source 'MyOrg_MSCRM' for the report server or SharePoint site is not valid. Browse to the server or site and select a shared data source. (rsInvalidDataSourceReference)"
I have to manually set the DataSource from within SSRS to /MyOrg_MSCRM/CustomReports/MSCRM_DataSource to get it to work.
2) The report doesn't appear under "Run on Selected records" but under "Run on All Records", and doesn't perform any prefiltering.
Also, when I download the .rdl from SSRS it hasn't modified it, neither adding an extra parameter or changing the SQL query. as I would have expected based on this information.
What could I be doing wrong?
I'm using MS CRM 2016 update 1 (v8.1.0.359) on premise, with SQL Server 2014 Reporting Services and the SRS Data Connector installed on the same machine.
Apparently, you can use a shared data source reference, but you have to name it MSCRM_DataSource, just as the Data Source that MSCRM uses for its reports.
If you upload a Report in MSCRM like this, MSCRM recognizes this and automatically updates the data source to the valid /MyOrg_MSCRM/CustomReports/MSCRM_DataSource datasource, and also adds the prefiltering modifications.
You've created a Shared Data Source that you are using for multiple reports. When uploading reports through CRM this is not supported. Each report must have its own connection details embedded in the report.
I think the reason for this is, as you are trying to do, the report gets modified to add hidden CRM parameters and to alter the queries so that pre-filtering can take place.
To fix this, you have to modify each report and enter the Connection Details directly into the report rather than using a Shared Connection. Its a little annoying but should give you the results you are expecting to see

TFS 2013: Uploading new report

We have a fully working TFS 2013 and have access to the default reports of the process template that we are using. Now we created a new report and try to make it appear in the team explorer of VS2013. Searching the internet indicated that the only possible option would be to download the process template, change the reporting part (e.g. adding the new report as default report) and then upload the "default" reports then via command line tool (tfpt addprojectreports ...)
Since changing (including adding) areas, iterations and other stuff can be done in the "live" system (without editing the process TEMPLATE), it is hard for me to believe that there is no way to add reports without changing the process template.
Does anyone know how to upload a new report? Of course, in the end we would like to see the report in the team explorer...
try http://yourReportingServer/Reports/Pages/Folder.aspx
then navigate via collection, project to the folder you want the report to show up in, then "upload file".
You can directly upload the .rdl file to SSRS of your TFS instance.

How can the CustomerRef field from SalesTable be added to the CustAccountStatementExt report?

In Microsoft Dynamics Ax2012 R2 I want a customization for report CustAccountStatementExt by adding the field CustomerRef from SalesTable
Location of report in the AOT :
SSRS Reports\Reports\CustAccountStatementExt
You have to open Visual studio 2010 (only supported version for AX 2012 R2) and open this repot from Application Explorer (View -> Application Explorer Ctrl+D,Enter).
MSDN:
Walkthrough: Customizing Existing Microsoft Dynamics AX Reports
How to: Customize a Report
Visual Studio Tools for AX must be installed from the AX Setup.
In addition to Matej's answer (which only covers the customization of the report layout) you also have to make the field available in the report data source. To do that you have to add a new field to table CustAccountStatementExtTmp that will hold the value of the CustomerRef field from table SalesTable.
You will also have to customize the creation of the CustAccountStatementExtTmp records which in this case is surprisingly done in the report controller class CustAccountStatementExtController (usually the report tables are filled in the data provider class). This will require some work, because you have no direct way to access the SalesTable record there. Basically you have to figure out how to determine the sales order from the CustTrans record that is available there.
After that, you still have to customize CustAccountStatementExtDP.insertNewRecords method because for some reason the records are copied from one instance of the (temporary) table CustAccountStatementExtTmp to another.
After that the new field should show up in the data set of the report in Visual Studio and you can then include it in the report layout (see Matej's answer on how to do that).
Here are the steps I followed to accomplish this:
Add field to the CustAccountStatementExtTmp table
Add code to CustAccountStatementExtController.insertCustAccountStatementExtTmp method to populate the new field.
Refresh the data source in the SSRS report, and in the report design (and then re-open the design).
Add the field to the report
At this point I also had to restart the AOS before the data would appear on the report. Apparently there was something cached in memory that prevented it from working.