Mobile Report Publisher Blank page on preview with parameters - reporting-services

So, I'm trying to make a mobile report with parameters in Mobile Report Publisher.
My dataset is so big and i want to load in my repport only specific items by default.
I define my parameters in my dataset. I find my parameters in the report editor. But when i bind one parameter with one of my selected item, i got a problem. My selection list does not care about my parameter. When i enter in preview mode, i get a blank page.
For information, i foloow the MS tutorial : https://learn.microsoft.com/en-us/sql/reporting-services/mobile-reports/add-parameters-to-a-mobile-report-reporting-services
Even if i write default values in my report's parameters, it do not care about them.
IMG : My parameters binded with my selection lists and my parameters in my DS and my blank page preview
Thanks for helping !

We've had to set our dataset parameters to allow nulls and then the sprocs deal with those else it caused problems in the mobile designer

Related

Don't produce report if there is no data - PDF

I have a report for which there is sometimes no data to output. This report is run along with several other reports and all are then output to PDF. However, this report still produces the header and footer with a blank page even tho there is no data.
I can move the header and footer into the report and have tried to hide those elements with =if(rownumber("PersonalProfile")=0, True, False) in the Hidden property of those elements. It hides everything so now the page is blank, but it will will output a blank PDF. Is there a way to completely suppress the report?
I'm using 2008 and I don't see a Report Visibility property. All the data for the report is inside a single Tablix which is inside a rectangle.
There are 3 datasets: PersonalProfile which contains the meat of the data; BoardNames which just produces the name of the board for the report; BoardMeetings which allows the user to pick a date parameter.
If you are distributing your report using subscriptions and you have Enterprise Edition, then you can look at using Data Driven Subscriptions which will give you control over how and when reports are distributed based on whatever logic you need. Otherwise, there is no way to do what you are asking - as trubs says, Reporting Services must first render the report before it has any knowledge of whether there is any data to display.
You haven't explained how you are "running the reports" (e.g. manually in Report Manager, report subscription, third party app using URL access) - if you do perhaps someone can suggest a workaround.
There is no way to do what you want. ssrs has to produce the report in order to determine there is nothing to display.

Adding a text box for report description before the report executes

Is it possible to add a report description (text) near the parameters area, before the report is run in the Report Builder 3.0. Essentially, when the users click the report and right before they run it, I want to provide them with a small description of what the report does and what the parameters. I can do that in the footer but it wont help, because the footer is only generated after the report has executed. Please let me know.
Thanks.
This is not possible with the default SSRS interface. You'll have to wrap SSRS with your own interface to add this.
To build your own SSRS interface, you can use a few different methods, such as embedding a ReportViewer control in a Asp.NET application, or using URL access in an iframe. See How to change the SSRS input parameters position in report
Of course, with Javascript and client side DOM manipulation, you probably could sneak your content into place, but it's not a supported option.
The main problem is that you can't show a report if parameters are needed for it until those parameters are chosen. If you don't want to provide default parameters another way to solve this problem is by actually having 2 reports.
In report #1 you put the parameters and the text box of instructions, but nothing actually using those parameters.
In report #2 you put the parameters and the actual report.
At the bottom of report #1 have a button, that just goes to report #2 passing the parameters selected.
I've used this technique to provide instructions on parameters when I want a quick-and-dirty solution (as opposed to a proper solution such as what Jamie suggested with embedding)

I want to display a report on a web page The report needs a single parameter (prompt, possibly)

I want to display a Microstrategy report on a web page The report needs a single parameter
I have a report that has a (local) filter which I'd like to able to parameterize. Not the whole filter string but just the numeric value that the report filters on.
I know that I can use a prompt to put a value into a report, but I need to do this from an HTML document which, I understand, can't be done with a prompt.
Is there another way to do pass a parameter from an HTML document into the filter of report in the HTML document?
Kind Regards,
Barrie
If you're using a URL to the report, you can pass a prompt answer in as a parameter, specifically valuePromptAnswers.
TN15734 on the MicroStrategy Knowledgebase gives a full example, if that isn't clear enough.

How to display full URL when setting report parameters

I have a report (in SQL Server Reporting Services 2008) that has multiple parameters, but works very well. However, one of my users (my boss, of course) wants to be able to e-mail a link to the report using the parameters they have specified. They do not want to send the report itself, but just a link to it. However, as you set parameter values and click "View Report", the URL shown in the browser does not contain the parameter values in the querystring (just the default report path), and therefore is not really usable.
I know that this functionality is possible, because if I add a subscription to the report, and check the "include link" checkbox, I get an e-mail with a link like this:
http://servername/ReportServer/Pages/ReportViewer.aspx?%2fRoot+Action+Analysis&ShowChart=2&sPN=&iDept=All&rs%3aParameterLanguage=en-US
Is there a server setting that could be changed to show the FULL URL (with parameters) as users generate new reports?
Thank in advance!
I don't know how to change the settings so that the full URL is shown.
As a workaround you could add a textbox to the bottom of your report, and build the URL yourself in an expression by concatenating Globals!ReportServerURL, Globals!ReportFolder, Globals!ReportName, Globals!Language and your various Parameters.

ReportViewer Web Control and Dynamic Connection Strings

So I have a report in Reporting Services 2005. In it is one parameter (ConnectionString) which determines which data source the report will use. It also has several other parameters which are dropdown lists derived from the data source chosen in the ConnectionString parameter.
In Report Manager, this works great. All of the dropdowns are greyed out at the beginning. When you choose your data source, the page requeries/repaints and all of the available parameter values for the other parameters are filled in based on the queries for those fields.
However ...
In the ReportViewer web control, when the report is first loaded up, instead of dropdown boxes all of the other parameter fields are just empty textboxes. Choosing a different data source for the ConnectionString parameter doesn't requery/repaint the other parameters.
I've been flipping through the ReportViewer programming reference to see if there's some way to replicate the Report Manager's way of reloading the webpage with the report viewer upon certain parameter changes, but I can't find anything there that isn't over my poor little .NET head.
Any ideas?
Not sure if this is any help but I do have a suggestion. I would try pulling the logic for dropdown boxes out of the report and put them in an ASP.net page. Then pass the parameters to the report and control the rendering/refreshing.
HTH
UPDATE: So it turns out you must provide a default value for any parameters which in turn affect other parameters in your report in order to get the dropdown box to load properly on initialization. Also note this is recursive - so if you have a parameter which affects another parameter which affects another parameter, both the first and second parameter must have default values.