A Quick Report running a Crystal Report keeps prompting for full database Login Information, like username, password, DB instance, and schema owner, every time it's run, rather than authenticating automatically.

All FAQ questions / Reporting and analytics

Answer

A few specific setup steps commonly need checking together: use the proper IFS-provided VIEW for the relevant table, found under IFSAPP > Views, rather than referencing the underlying raw TABLE directly in the Crystal report; add the CR_WEB_INIT initialization call, found under IFSAPP > Qualifiers > CRYSTAL_WEB_UTIL_API, to the report; apply the correct table-aliasing convention by renaming or prefixing the report's table references with either a backslash or an _A suffix, per IFS's own Crystal-report aliasing convention, which lets the framework automatically supply login credentials for that aliased view; update the report's table linking to match the renamed/aliased tables afterward; and add the OBJVERSION field to the Report Header, suppressed/hidden from the visible layout, so the framework's own automatic-login mechanism has what it needs from the report definition to correctly authenticate without prompting the user.

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