Hi all,
I have subreport in the header area that I can’t get to render. The subreport runs fine when I add it to the site menu and run it separately. I have an almost identical subreport running fine in a detail section (see below).
I even tried putting the second subreport in a detail section.
Lastly, if I add a field to the subreport header or footer, those fields show up. Any thoughts?
Best answer by Steve Milner
@jamest62 Valentyn's read fits what you're seeing. When a subreport's query comes back empty, its report header and footer still print, but no detail rows do.
Standalone, the subreport gets its parameters from the prompt. Embedded, it gets them from the SubReport's Parameters list. Your footer test checks the main report's side of that handoff, not the subreport's.
To see what actually arrives, open the subreport, add a text box to its report header with =[@YourParam] for each parameter, and run the main report. The report header prints even when the query finds nothing, so it'll show exactly what the subreport received.
- Blank, or the subreport's own defaults: the values never arrived. The subreport fills each of its parameters from the row in the SubReport's Behavior > Parameters list with the same Name. If a Name doesn't match, the report still runs with no error, and that parameter keeps its own Default Value. The match isn't case-sensitive, so look for spelling differences between each Name and the Parameters tab of the subreport's Schema Builder.
- A value, but not the one you'd enter in the prompt: the handoff works, so fix the ValueExpr. For an ID field, [Table.Field] hands over the CD you see on screen, not the internal ID. If the subreport parameter is an Integer that filters on the ID, pass =Report.ExtToInt('Table.Field', [Table.Field]) and set Type to Integer on that row.
+7Hi
Without the report and subreports themselves, it's hard to say what the root cause is, but most commonly it happens because the subreport returns no records. Since you've already confirmed it works on its own, as a next step I'd suggest checking whether the parameters are being passed properly. To do that, add those parameters to the same report section and see if they render values there. If that works, make sure you're passing them to the subreport correctly and that the subreport is actually using them. If none of that works, I'd try putting the report into a different section to see whether the behavior changes.
Hi
Without the report and subreports themselves, it's hard to say what the root cause is, but most commonly it happens because the subreport returns no records. Since you've already confirmed it works on its own, as a next step I'd suggest checking whether the parameters are being passed properly. To do that, add those parameters to the same report section and see if they render values there. If that works, make sure you're passing them to the subreport correctly and that the subreport is actually using them. If none of that works, I'd try putting the report into a different section to see whether the behavior changes.
Hi
Thanks for the quick response.
Yes, I have verified the parameters are passing. Added them to the Foot section and they should on the main report.
+7
Would you mind sharing the main report and subreports here so I can play around with them?
+7@jamest62 Valentyn's read fits what you're seeing. When a subreport's query comes back empty, its report header and footer still print, but no detail rows do.
Standalone, the subreport gets its parameters from the prompt. Embedded, it gets them from the SubReport's Parameters list. Your footer test checks the main report's side of that handoff, not the subreport's.
To see what actually arrives, open the subreport, add a text box to its report header with =[@YourParam] for each parameter, and run the main report. The report header prints even when the query finds nothing, so it'll show exactly what the subreport received.
- Blank, or the subreport's own defaults: the values never arrived. The subreport fills each of its parameters from the row in the SubReport's Behavior > Parameters list with the same Name. If a Name doesn't match, the report still runs with no error, and that parameter keeps its own Default Value. The match isn't case-sensitive, so look for spelling differences between each Name and the Parameters tab of the subreport's Schema Builder.
- A value, but not the one you'd enter in the prompt: the handoff works, so fix the ValueExpr. For an ID field, [Table.Field] hands over the CD you see on screen, not the internal ID. If the subreport parameter is an Integer that filters on the ID, pass =Report.ExtToInt('Table.Field', [Table.Field]) and set Type to Integer on that row.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
