Two Custom Menu items trigger the same Crystal Quick Report, but each needs a different fixed True/False value passed to a Crystal parameter (to show or suppress a Summary section) — without letting the user change that parameter at runtime. Passing a literal static True/False value to the Quick Report parameter doesn't work as expected — what's a working alternative?

All FAQ questions / Reporting and analytics

Answer

Instead of trying to pass a literal static value, control whether the parameter is populated at all, per menu item: for the menu item that should show the Summary, map the Quick Report parameter's Source Key Name to a real field that's always populated on the record (like Line No) — guaranteeing the parameter always has a value; for the menu item that should suppress the Summary, simply don't map that Quick Report parameter at all, leaving it null. Inside the Crystal report itself, use an ISNULL() check against that parameter to decide whether to show or suppress the Summary section — this achieves the same per-menu-item fixed behavior that trying to pass a literal static value directly couldn't.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Reporting and analytics questions