I am using SSRS 2005. I have one parameterised report. I am using 3,4 cascading parameters. my last parameter can have upto 5000 values in it. I want to know that what is the maximum limit of multi-value parameter becuase when i select deselect some parameters I got one error "Operation is not valid due to the current state of the object." I wonder if it is due to lot of values in one of the parameter.
Please guide.
Thanks
I can't find a source for a hard limit of number of parameters but to be honest if you're using 100s I think you're going to run into usability issues first.
I'd suggest grouping the options by one or two more cascading parameters that narrow down the range if that's possible for your application.
From here
There is a constraint (on .NET framework or Web server I think) that allows only 1,000 values to be loaded under parameter drop down boxes
Related
I am receiving the following error from my child report: "The report parameter 'prmDefaultValueForSnapShots' has a value of DefaultValue or a ValidValue that depends on the report parameter 'prmStoreName'. Forward dependencies are not valid."
I have a parent report that feed values to the child report to display all sales data for the specific store. However, this report is rather large, thus I'm trying to set a snapshot for it on the Report Manager to execute in the early mornings for better user experience. For the snapshot to work, I need a default value on the parameter and I have been unable to make it work.
If anyone has any idea how to resolve this particular issue. Please, give me any suggestion as you can.
Regards,
Marcus
I have been researching this issue since Tuesday and I have not had any luck.
I'm not entirely sure I understand your goal or configuration. I'm also not sure if prmDefaultValueForSnapShots and prmStoreName are parameters of the main report or the sub-reports, and which of the two throws the error.
However, this error may occur if a parameter depends on another parameter which is not yet provided. Note that the order of the parameters is important. By "order", I mean the order in which they are defined, which is also the order in which they appear in the list (you can reorder them using the arrow buttons).
Is it possible that prmDefaultValueForSnapShots depends on prmStoreName, but is defined before it?
I'm trying to replicate a report from old Oracle Discoverer to OBIEE.
The issue is that when I had the "pivot table prompts" to the OBIEE analysis. I'm left with duplicates instead of unique values in the drop down field. Can anyone explain how I can keep this from occurring? This only happens when I add three or more attributes/columns to the "pivot table prompts" section. This worked in Oracle Discoverer….
Be sure, for the physical connection you have defined, that you have checked the below option:
Also, I know there was a bug around this sort of functionality occurring if the column properties were set to repeat, but that is not a common thing people do, and is probably not your scenario, but it is worth a look: Bug 13147411 : 11G PROMPT IS DISPLAYING REPEATING VALUES WHEN ITEM PROPERTIES SET TO REPEAT
As mentioned by rmoff, incorrect keys can often lead to this issue. As he said, you can check the nqquery.log to see the physical SQL, or enter SET VARIABLE LOGLEVEL=4; in the SQL prefix on the advanced tab, then run your report again. This will generate a log in the admin pane of the tool that you can check easily.
The dropdown list is built from the dimension you have defined, so if your key is incorrect you'll get duplicates. Check the physical SQL in nqquery.log if in doubt to see what SQL OBIEE is generating that returns the duplicates, and make sure you have defined your logical dimension correctly.
The issue was resolved by moving "Repeat" to "Suppress" for the individual columns that I was prompting on in the pivot!
We did this a lot throughout my department because we use the exports for further manipulation rather than using OBIEE only for high level overview and summation. Each row must hold the value in order to filter, so the "Repeat" functionality is often selected.
Thanks for the help/answer!!!
I am using SSRS 2012.
I have two datasets. I have two tables.
The first table contains a contract Id which is used as parameter in the second dataset.
I want to set the parameter as the contractId (ie Fields!ContractId.Value, or ReportItems!Contract1.Value) or something like that but nothing works because of different limitations.
If I would be using a subreport that would have been easy just pass the Field!Contract.Value from the 1st dataset as the parameter for the second and there you go. But since we want to call the report using SQL server agent, I cannot use subreport since the agent is limited and does not accept subreport.
So I believe my only option is to use two different tables, but I still need the value from the first dataset. Also, I don't think LookUp() would work for me as I do not have Ids.
Does anyone already did something like that?
Thanks for any help.
You can create report parameters in which the available values are pulled from a query.
Then just use the parameter in your second data set.
I'm putting together an SSRS report in BIDS 2008. I've got a parameter - we'll call it ParamA - that's set to allow multiple values, and, in Available Values, I've set it to 'Get values from a query'. When I run the report, I get the following error:
An error occurred during local report processing.
The definition of the report '/Report2' is invalid.
The report parameter 'ParamA' has a DefaultValue or a ValidValue that depends on the report parameter "ParamA". Forward dependencies are not valid.
When other people get this error, it seems to involve multiple datasets, and the forward dependencies always deal with two different parameters. I'm using only one dataset, and only one parameter is cited in the error.
Any advice would be great.
Have you checked the order of your parameters in the report designer toolbar. If they are ordered incorrectly the report will fail because of the order required to make the dependencies work. You use the little blue up and down arrows to set the order of report parameters
I think I figured out the problem. Using a multi-value parameters requires that each such parameter have its own dataset. I only had one dataset, and I was trying to point the MVP at it and run the report off of the same set. I don't know why that doesn't work, but I added a dataset for the MVP, and the error went away.
I want to group by a report item, but that's not allowed.
So I tried creating a parameter...not allowed as well.
Tried referencing from footer...failed again.
This is somewhat complicated.
Let me explain:
I have textbox22, it's value is:
=Code.Calc_Factor(Fields!xx.Value, fields!yy.Value...)
This is embedded VB code in the report that's called for each row to calculate a standard factor.
Now to calculate the deviation from the standard factor, I use textbox89, whose value is:
=(Fields!FACTOR.Value - ReportItems!textbox22.Value)/ReportItems!textbox22.Value
Don't get confused between Fields!FACTOR.Value and textbox22.Value, they are different.
Fields!FACTOR.Value is the factor used, textbox22.Value is what it should be (standard factor).
Now I want to create a group which splits deviations into 2 groups, > 1% or not.
So I tried creating a group:
=IIF(ReportItems!textbox89.Value > 1,0,1)
...But then SSRS complains about using report items.
I have run into a similar problem of using report items in the past, but this is a new case!
Any help greatly appreciated.
Have you tried adding a calculated field to your dataset?
Here is how it works:
While you are in the layout view of the report, open "datasets" tool window(in my environment it is on the left).
Right click on the DataSet you are working with and add a field, you can use a calculated field, and build your formula appropriately
Then you should be able to group on this field
-Dan
I'm not 100% that someone won't have some magic solution for this but I have run across similar problems myself in the past. I believe (but could be wrong) the problem Reporting Services is having is that it only renders once and what you're asking it to do is render the data before rendering the grouping which it doesn't do.
The only way I have ever been able to produce the exact results I need is to make the data rendering happen exclusively in the SQL (through the use of table variables usually) and then use Reporting Services merely as a display platform. This will require that your factoring algorithm gets expressed in the T-SQL within the stored procedure you will likely have to write to get the data in shape. This would appear to be the only way to achieve your end result.
This has the bonus feature of separating report design and presentation from data manipulation.
Sorry I couldn't provide a SSRS solution, maybe someone else will know more.