I have what I thought was a very basic SSRS scenario. I have two datasets in my SSRS 2008 report; dsMTD and dsYTD. They both contain the same columns, the only difference is the SQL statement that fills them both (but I don't imagine that's really relevant to the problem).
I have a textbox on my report, and I wanted to show the SUM of a certain column within the report. I tried to make my expression as follows:
=Sum(Fields!cost.Value, "dsMTD").ToString()
This works fine in SSRS 2005, but the expression in SSRS2008 gives an error of "Unknown Collection Member" on the field reference in my expression.
Am I not doing something right? I've recently installed CU6 for SQL Server 2008 on my machine, and wonder if that has changed something?
Just ignore this. The error is just misleading I assume. At first I was running and my dataset actually had no rows, which explained why a value wasn't coming back. I intially thought this was connected to the "Unknown Collection Member" error, but when trying to a different dataset that does have data, I still get that error, but also get the correct value.
I'll try and ask for help on things that actually are wrong next time!
Related
I have a report, that used to have columns in the following order [A,B,C,D,Banana,E]. I was then asked to make some changes to my report, which I did so that the report columns now has an order of [A,Rocket Ship,Banana,B,C,D,E].
When I look in Visual Studio or look at the report on SSRS, I see the correct order, HOWEVER, when I let the subscription run, I see that it is still putting out reports with the wrong columns. Has anyone else seen this phenomenon? I've tried creating a brand new subscription, but I still get the old Column order.
Any help is greatly appreciated.
Check to see if the report using any caching or snapshots.
It might be using an old copy - though I would think it would be the same as one rendered manually from Report Server.
The issue is that the CSV report that is created isn't dependent on the report that is created with SSRS. Essentially, it just spits out the results of the SQL query into a CSV file.
I have an Access 2007 report which has a table as a data source. I have a few columns of data that directly pull data from the table in a summarized way (using report groups) and the last column is the total of the first 6 columns. Simple enough.
Now the expression that calculates the sum of those 6 columns sometimes returns #NAME? and sometimes does not. I have more than triple-checked for any error, typo, whatever.
There is no space in front of my expression;
The expression does start with an =;
The references to columns in the table are all valid;
No control has a name even remotely similar to any column in the source table;
I have tried generating the expression using the expression builder;
There is no conditional formatting tied to any control;
There is no VBA code used at all in generating the report.
Also, sometimes if I copy the one of the boxes with #NAME?, delete it and paste it back then all the #NAME? errors disappear. Then I save and reopen the report and the errors are back.
I'm out of ideas for this. I can't post screenshots or distribute the file due to its nature.
Thanks !
I had similar problems...The solution was that I have used unicode characters in Names. For example a Text Box with the control source "dataščž" had the Name "datačšž". This was working in previous versions of Access, but not anymore. Changing the Name "datacsz" solved the problem.
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.
Issue I get for one of my shared data sets only on certain parameters. If the parameter returns nothing for that dataset then I seem to come across this problem, there is a tablix in this report that uses the shared dataset and if I remove the tablix but keep the shared dataset I still get the error on the report preview.
The dataset uses a MDX query (SSAS) to get its data, if I run the query from the query designer it returns 2 rows but the dates in the rows are outwith the scope of my report so the report would return 0 and I assume thats my issue.
Anyone got any ideas/tips?
Uses SQL Server 2008 R2
Thanks
Managed to get round this issue by having an embedded data set rather than a shared one.
Gets around the issue, very annoying though!
I have a report working well where I extract the number of logins per user. Each login takes up one row on the report.
I have date parameters and my DB goes back a year. However it seems the report will only show 40/50 rows despite a report expecting to deliver, say, 250 for the amount of times I logged in.
Is there some setting in reporting services that limits the number of rows delivered. Can't find it anywhere..
Thanks.
The answer to your question: nope, as far as I know there's no real equivalent of SQL's TOP 50 statement in SSRS itself.
Some things that come to mind that may be causing your symptoms / can be investigated:
What happens if you run the query for the dataset in SSMS? Be sure to fill in the exact parameters the report's using (if any).
Run the query as a test from SSRS designer. If you're using Visual Studio: right-click the dataset and hit "Query...", then hit the red exclamation mark and fill in any parameters if needed.
Try putting a CountDistinct call (on your dataset) in a textbox somehwere in the report, by itself.
Check the filtering and grouping on your tablixes, perhaps even by looking at the XML source code for the RDL.
Show the parameters in textboxes (oldskool printf debugging! :D) to make sure they're what you expect them to be when the report's run on the Report Server. If they're not: try deleting the report on the server and re-deploying it.
Have a look at the ExecutionLog2 View in the ReportServer database, specifically the Number of Rows returned.
As mentioned in the comments by Atilla: You may also monitor exact SQL SSRS sends to server using SQL Server Profiler.