Linking an SRSS report - Dropdown parameter not getting passed - drop-down-menu

Sorry if this is a duplicate post, not sure what happened with my original one.
I have a linked SSRS report (Report A) that links to Report B. One of Report B's parameters is controlled by a Dropdown/ComboBox. In the parameters dialog box that gets launched from the navigation tab, I have tried both 'VALUE' and simply putting VALUE without the single quotes.
Both ways result in an error stating that the parameter was not provided. How do I correctly pass this value, so that Report B will recognize it?
Thanks

Related

SSRS Expression to Open Specific Report

I have a SSRS dashboard that has a calender image on it and under the image properties I have an action to Go to Report and a specific report was listed. Depending on the measure the user is looking at in the dashboard when they click it a 12 or 24 month trend chart will load. It works fine when I just have it set to go to a specific report but when I put an expression into the Specify a Report option I get a weird error that I have been researching but the error seems possibly misleading so I thought I would just put the expression I am using out here to see if anyone has any direction for me as it seems like what I am trying to do is simple but I may be searching wrong. Thanks in advance!
I have the expression opening the 24 month chart of the definition type is CSH and eventually it will check for other conditions but I wanted one to work before I went on.
=IIF(Fields!MEAS_DEFINITION_TYPE = "CSH","FITDash_Trend24mo.rdl",Nothing)
I get this error and it started up after I added the expression above. The datatype of MEAS_DEFINTION_TYPE is nvarchar(25):
Severity Code Description Project File Line Suppression State
Error [rsCompilerErrorInExpression] The ActionInfo.Action.Drillthrough.ReportName expression for the image 'Calendar25' contains an error: [BC30311] Value of type 'Microsoft.ReportingServices.ReportProcessing.ReportObjectModel.Field' cannot be converted to 'String'.
Common mistake, you have forgotten to specify the .Value property of the field
Try
=IIF(Fields!MEAS_DEFINITION_TYPE.Value = "CSH","FITDash_Trend24mo.rdl",Nothing)

Infopath validation issue

I experienced the following validation error today using my Infopath form via a SharePoint 2013 list:
'The form cannot be submitted because it contains validation errors. Errors are marked with either a red asterisk (required fields) or a red, dashed border (invalid values). Field or group: my:group1 Error: Cannot be blank
Click OK to resume filling out the form. You may want to check your form data for errors.'
I have no idea where to locate this 'group1' because I am pretty sure it doesn't exist!
I have gone through all the fields - never experienced this before. I did look over the web and found someone mentioning lookup tables via another list - but I do not have any look up tables.
Any suggestions greatly received.
Andy
I had the same issue. It is one of two things.
You have a required field and are using a rule to hide the section. Infopath is not intelligent enough to realize the rule should not error on the field that is hidden. The way to fix this is to remove the required rule and then instead add a validation rule on the field that you are trying to hide. For example if "Field 1" is Yes and Field 2 (the hidden one) is blank, then show error message.
The second one is a bug that occurs after changing a fields type. You may need to delete the field Group 1 and then recreate it.

OBIEE Column selector with no results

I'm trying to create an analysis based on errors, so I hope I have little to no value in this analysis but I need a column selector to switch between different measures which can have an error.
When I switch to a measure which doesn't contain any errors, I get a nice 'no results' message but also my column selector disappears. How do you keep this even when the analysis results in 'no results' or maybe another way to work around this.
Thanks!
a) "Back" in the browser :-)
b) "Clear My Customization" in a dashboard context
c) Instead of a column selector, you can move that logic to a dashboard prompt which switches out the measure in the analysis itself. Since the prompt isn't in-line with the analysis code but a stand-alone object it will stay unaffected by "No results".
You'd say '"Measure"."#{vMeasureSelection}{Count}" in the analysis column formula and then have the presentation variable value from a prompt passed in there.

Hiding parameter prevents other parameters from refreshing

I have the first parameter (client drop down) that passes an ID to the second parameter to be used in the 3rd and 4th parameter. During testing all the parameters are set to visible to verify what's being passed. As soon as I hide that second parameter the rest don't refresh. Again, visible, correct info flowing through, hidden, DOA. I have this set up exactly like this on at least a dozen other reports with no issue. I'm not real sure where this going wrong since I can see the correct value being passed while visible?
I was able to duplicate your issue. While I can't find a reference to support my supposition, I believe that hidden parameters (even those with a default value) are not evaluated until rendering, which would explain this behavior. Data sets that drive parameter values are run prior to the report being rendered.
As you're talking about having trouble with dependencies between the parameter values, I assume you're using queries to drive your available values for parameters three and four. If this is the case, then simply embed the logic that relates the value(s) of parameter 1 to the value(s) of parameter 3 into the query that drives parameter 3's available values. By cutting out Parameter 2 and incorporating it into the query logic for parameter 3, you will work around this issue.
If you're having trouble accomplishing this, reply in a comment and I'll see if I can help. As it stands, I don't know enough about what you're trying to do to help any more.

Parameter Validation on Reports

I'm new to SSRS, so I apologize if this question is too simple:
I have a report which accepts a parameter called "Amount". I want to constrain valid inputs to currency values >= 0, and pop open an error message if the user enters improper values.
I don't want to validate inputs in my stored procedure and throw exceptions, because SSRS displays a very generic "Query execution failed for 'someTable'" message to users who access the report from another machine, and my business does not want to turn on the "Enable Remote Errors" flag.
How do I add input validation to report parameters and notify users of bad input?
Yes, I've googled around, but haven't had much luck. Thanks in advance :)
Okay, how about this?
All you have in SSRS, really, is the SQL query and expressions in report fields.
Perhaps you could add a big, red text box at the top of the report for your error message, and give it an expression like '=IIf(Parameters!Amount.Value < 0, "Error: Invalid Amount", "")'.
Then go to your table's "Hidden" property and give it the expression "=Parameters!Amount.Value < 0"
You could also add into your query's where clause and add "AND #Amount >= 0" so you aren't fetching from the database when there's an error.
It's possible to make report parameters in SSRS that are based on a particular list or a lookup query but I don't think you can apply a regex or something like that.
Instead you might consider separating your report into two panels, one which displays your report and one which displays an error and then you create an assembly with a function in it that validates the parameters for the report before it is run. If the validate parameters function is successful you hide the error panel and show the report panel, if not you do the opposite.
I don't think there's a whole lot you can do in the reporting tool itself. It's pretty rudimentary.
However, you can provide an ASP.net web interface or a form that you can use to ask the users for the parameter values in any format .NET allows, and use the ReportViewer control to display the report. It sounds daunting, but it's actually pretty straight-forward, particularly if you already have a project you can build on.
Microsoft gives tutorials for using the ReportViewer controls.

Resources