Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The problem is that your procedure's definition creates to two parameters: <code>TYPE_ID</code> and <code>SUBTYPE_ID</code>. Crystal Reports' parameters (dynamic or static) weren't designed to interact with each other.</p> <p>As I see it, you have three options:</p> <ul> <li><p>create a report w/ the <em>single</em> prompt group (make sure that the prompt group creates two parameters) that you want (the main report doesn't require a data source, btw); insert a subreport that uses your procedure (it will create two parameters); link the parameters in the main report to parameters in the subreport; if necessary, you can create formulae in the main report (which are then linked to the two parameters in the subreport) for extra logic (convert a parameter value of 'All Type Id' to NULL, for example).</p></li> <li><p>refactor your procedure to have a single <code>VARCHAR</code> parameter that will receive a concatenated <code>TYPE_ID</code> and <code>SUBTYPE_ID</code>. Create a dynamic parameter that will have a concatenated value for the key and for the description (e.g. 1/3; Type [1] - Subtype [3]). Your procedure's logic will need to parse the parameter's value to determine the values of <code>TYPE_ID</code> and <code>SUBTYPE_ID</code>. You'll need to create a query that generates the keys and descriptions, which will be exposed through a BusinessView's various layers.</p></li> <li><p>abandon the procedure in favor of a Command or 'normal' query. in my experience, <strong>the vast majority of reports can be build without a stored procedure</strong>. Combined w/ a single prompt group, this will give you the flexibility that you need.</p></li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload