SSRS 2005 Subreports is sometimes empty
I have a Parent report that intentionally displays nothing, but asks for a dataset from a number of jobs for billing. This parent report then scrolls through these assignments and submits them one at a time to two sub-regions. The first SubReport is a summary of what will be billed for the completed job. The second SubReport is a breakdown of all the details for this Invoice, Employee, Hours, Rate, etc.
The parent subdivision SubReports will feature about 400 jobs. The short report prints beautifully for everyone. The detailed SubReport does this about 90 to 95% of the time, but on some jobs it is empty and I see an error saying the SubReport cannot be displayed.
When researching this, the most common answer is that there is a problem with how this parameter is passed. This doesn't seem to be the case, especially considering that around 380+ of the 400 assignments are shown in detail beautifully. So, I ran a specific request for this SubReport to see if I actually got the data for one of the offending jobs. Yes, hundreds of rows of data, so there is data, only one parameter is passed.
What else could be causing this error?
The report continues after the error, so that's fine, but I need these detail sheets to display.
source to share
This issue has been resolved. I am posting my solution here for anyone who might be experiencing something similar, although it seems like a rather strange circumstance. The problem is with the Hidden property being applied to various table elements.
In our company, task groups are assigned to programs. The program manager for one of these programs wants to see revenue subtotals grouped by "subheadings" in his program. Nobody wants to see it anymore. My solution was to create fields in the report (in the offending table) that have the visibility property set to true ONLY when its program is reported.
The grouping for these reports is Program / Job / SubJob. I have applied the hidden property to various fields of the table using an IIF statement. If it's his program, show the data; otherwise, no. As it turned out, something in SSRS 2005 was in conflict as a result of these hidden fields, but only on certain jobs, and this conflict was throwing an object not found exception when these jobs came in. I still don't know what a conflict is and why it doesn't always appear. About 95% of reports are printed normally.
The solution was to move all hidden values into one table column and apply the hidden property ONLY to that column. This way the entire column is hidden at will, and everything in it obeys a hidden property of the column itself.
source to share
To debug this type of problem, I take the following approach.
- Work out if it's a specific dataset. IE is a specific set of job numbers. You do this by limiting the request in some way (parameter, hardcode, etc.).
- If it is data related, narrow until you can find the actual date causing the problem.
-
If it is unrelated data, I judge the rendering technologies one by one.
- I use separate browsers first
- Then I start different report servers
- Finally, different viewers of the reports (native, direct, visual studio SharePoint, etc.).
I usually find this to be a minor data conversion problem that produces the next data stream.
Do not give up on errors in reporting systems - you, in my opinion, are using outdated technology.
NB Just because a subreport has its own on it does not mean that it will work in conjunction with the main report. The interaction of the different parts is also important.
source to share