on 10-27-2023 5:36 PM
While this was tested in Crystal 2016, I suspect this bug also exists in Crystal 2020.
The attached report (change .txt to .rpt) uses the Xtreme sample database.
It has one main report parameter (Country).
The on-demand subreport has two parameters:
1. a linked parameter based on the Country link from the main report.
2. an unlinked parameter for City
The bug: when the main report runs, it prompts for the main report Country parameter as well as for the unlinked subreport parameter. It should NOT prompt for the unlinked subreport parameter when running the main report. Reasoning:
1. the user may not invoke the on-demand subreport. So it doesn't make sense to answer for a parameter that is not required for the main report.
2. the user may want to trigger 2 different instances of the on-demand subreport, each with different values for the unlinked parameters.
And when running the On-Demand subreport, it does NOT prompts for the unlinked City parameter. It should prompt for that parameter.
Hi Jamie,
My users don't use a server platform. But the solution I just finished implementing follows a very similar logic to yours. A click on a report object launches a secondary report and passes to it parameters (and other arguments) based on the tooltip expression of the clicked object.
This approach not only avoids the problematic parameter behavior of on-demand subreports, but also allows for subreports in the triggered secondary report (Crystal doesn't allow subreports within subreports).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
9 | |
9 | |
8 | |
7 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.