The AllCrystalReportsSearchWrapper stored procedure (i.e. the stored procedure used by the Core Reporting Model) must receive several parameters from the user interface (User ID, Report ID, Select String, Where String, View Name), in order to display properly. However, the dashboard interface only passes through a single parameter (user ID). Thus, you must first create a shell report that only receives this single parameter, and then link it to the sub-report.
Notes:
|
Formula |
Update |
Parameter_RptID |
No change required; this formula should always be: 0 |
Parameter_SecWhereStr – no change |
No change required; this formula should always be: “” |
Parameter_SelectStr |
Update this formula. Copy the select string from the sub-report’s @SelectStr parameter into this formula field (refer to Step 2-3 in the section, “Download and Develop the Crystal Report”). The shell report needs to tell the sub-report that it wants to get these fields from the core reporting view. The formula should look something like this: "OrgUnitName,RCMStatus,ObjvName” The fields contained within the quotes are the same fields in the sub-report’s @SelectStr parameter.
|
Parameter_UserId |
No change required; this formula should always be: floor({RptDataShell;1.UserId}) |
Parameter_ViewName |
No change required; this formula should always be: RptConfigViewProcRskMatCoreSearch |
Parameter_WhereStr |
Update this formula. Copy the select string from the sub-report’s @WhereStr parameter (refer to Step 4 in the section, “Download and Develop the Crystal Report”) into this formula field. The shell report needs to tell the sub-report that it wants to filter the results from the core reporting model based on this set of parameters. The formula should look something like this: "AND ( [RCMStatus] IS NOT NULL )" where the text contained within the quotes is the same as the sub-report’s @WhereStr parameter. |