SSRS using a cube - parameter defaults messing things up - reporting-services

I created a report in SSRS (2010) using a SSAS cube (which is new to me). I added parameters using the "Query parameters" option in Query Designer.
The problem is, it makes me select a default parameter when it really isn't applicable to my report. The OK button is grayed out until I pick a default param.
Further, I went into the parameter it created (under Report Data->Parameters) and made it not need a default. My report didn't work properly. It uses all the choices from that parameter even though I selected 1 and hit "View Report".

Related

Is there a way for SSRS to remember my parameters when switching between Design and Preview mode?

When designing a report in SSRS, I put in my parameters and run the report.
If I see that there is a change in the Design that I need to make, I then have to flick back to the Design tab and make the change.
Once I go back to the Preview tab, I then have to again put in my parameters and wait for the report to run.
Is there a way to have SSRS remember the parameters that I had just entered and possibly keep the data in a cache so that when I flick back to the Preview tab, it just shows me the report rendered with my changes (but not new data etc)?
I'm pretty sure I can do this in Crystal Reports without having to re-enter parameters etc.
There is no way for SSRS to remember the parameters when flicking between the design/preview tabs - however you could select default values for the parameters so that when you flick to the preview page, the values will automatically appear in the preview tab.
To do this, right click the parameter > Go to "Default Values" tab > Select "Specify Values" and add the default values you would like to use

SSRS - parameter value change is not running my report again

I have a report with two params that are datetime, #startdate and #enddate.
I have set them up under "advanced settings" to "Automatically determine when to refresh" (also tried "Always refresh") for both of the parameters.
I deployed my report and ran it. Changed the date and it appears the report fires a postback (screen flashes and browser indicates activity bottom left corner) but I end up with a blank screen (I still have my breadcrumb up top but everything below is blank). If I hit the "view report" button on the end of the header area it will run it again but my intention is to re-run the report when either parameter changes.
Not sure what I did wrong. I'm using SSRS 2008 and this was something I was able to do in the past versions of SSRS.
If you hard code a default parameter value, like 1/1/2000, it doesn’t think it needs to refresh all the way (it gives you a blank report though!). The solution is to point it to a query (dataset) that selects a date valued at 1/1/2000. And I think for multiple parameters, you have to set all default values this way. Pathetic for sure.
you need to deploy your report, once before you pass the parameters and once after you pass the parameters. that fixes the issue for me

How to restore Override Default button for default value in SSRS parameters configuration

If I click on an Override Default button, a textbox appears. How do I get the Override Default button back?
(source: socha.com)
Re-deploy the report to that folder, and the default settings (and therefore the option to override them) will be restored.
Redeploying the reports does not change the parameter settings. I had to delete the report on the report server first and then deploy it again and than I had the button back.
One option is to find out what was set on the default field and re-add.
Example, I messed up one of my default values on a "Date" field.
Steps to fix:
Edit a similar report that had the same field/default value. (Click the down arrow on the report on the web interface and select Edit in Report Builder).
On the folder structure on the left expand Parameters and double click the parameter you want to fix.
Click Default Value on the Report Parameter Properties pop up window.
Click the fx button and paste the parameter you grabbed from the working report. In my case the string was =datetime.Now().
Only way is to delete report and deploy it again. you can make it quickly:
open report in report designer and keep it open
go to reporting service web and delete opened report
go back to report designer and click save buton (or ctrl+s)
More by accident than intention I fought this issue and discovered a method that was simple. I have only repeated it once but it had the same results.
On the SSRS Report Parameters Properties dialog in Report Builder:
Select the parameter that is the problem
Select "Default Values" tab
Select the "Specify Values" Dialog
Set the value to something valid
Select OK and run the report
When it is complete, set the parameter value to whatever you would like it to be going forward
save the report
Now, if you go into the web interface, select manage from the report's drop down menu. Then if you look at parameters section of the management tab the "Override Default" button should be restored.
End Note: The button's appearance seems to be tied to the object property
<DynamicDefaultValue>True</DynamicDefaultValue>
of the parameter. This is found in "Parameter" field of the "Catalog" table in the ReportServer database. To test the dependency I wrote a quick WPF app with an XML viewer that allowed me to browse the parameters independently. I created a dummy SSRS report and by adding and removing that node in the XML properties could make the button appear and disappear. If I get around to making the connection string dynamic I will make the app available in this post.

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.

SQL Server Reporting Services Default Values From Query not working in deployed report

In order to populate a textbox in a page header I am setting up a parameter (as you cannot use Fields) and referencing this in the textbox. The parameter has the Default Value set to "From Query" and the Dataset and Value Field are set accordingly. This works a treat in developmentt in Visual Studio 2005. Once I have deployed the report and am viewing the report in the ReportViewer control I get the error:
"Parameter validation failed. It is not possible to provide valid values for all parameters. (rsParameterError)".
If I remove the parameter, the report works fine.
(Strange thing is that I thought I had this working earlier).
You've probably checked, but has the default value copied over? I've had issues in the past with reporting services where the default values were lost when I moved a report from one box to another.
Thanks for the answer - it has pointed me in the right direction...I have been using my own program to deploy multiple reports so rarely look at them via the Report Manager website. Anyway - I just deployed the report on my home PC and it worked fine....looking at the report in Report Manager on both PCs I found that "Prompt User" on the PC that wasn't working was not ticked...go figure. Ticking this resolved the problem.
I am liking the results that I am getting from SSRS, but I am quite new to it and am finding some things (like this) a little frustating...mouse and keyboard are lucky to not find themselves thrown out the window!