A new Crystal Quick Report, built following IFS's own Crystal guidelines using the CR_WEB_INIT stored procedure and confirmed runnable as both IFSAPP and IFSPRINT with the right permissions granted, still prompts the end user for IFSAPP sign-on credentials when actually run through the client.

Q: A new Crystal Quick Report, built following IFS's own Crystal guidelines using the CR_WEB_INIT stored procedure and confirmed runnable as both IFSAPP and IFSPRINT with the right permissions granted, still prompts the end user for IFSAPP sign-on credentials when actually run through the client.

Grant access to the crystal_web_util_api package to the IFSSYS user specifically — this resolved this exact symptom. It's not something obviously implied by the standard Crystal report setup guidelines, but the framework's own internal proxy user needs this specific package access to properly handle Crystal Quick Report execution without falling back to prompting the end user for IFSAPP credentials.

Answer

Grant access to the crystal_web_util_api package to the IFSSYS user specifically — this resolved this exact symptom. It's not something obviously implied by the standard Crystal report setup guidelines, but the framework's own internal proxy user needs this specific package access to properly handle Crystal Quick Report execution without falling back to prompting the end user for IFSAPP credentials.

← Browse Reporting and analytics questions