Dynamic Destination Name (DESNAME) Using AfterPform Trigger Not Working In 9.0.x / 10.1.2
(Doc ID 280717.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Reports Developer - Version 18.104.22.168 to 10.1.2.3 [Release 9i to 10gr2]
Information in this document applies to any platform.
You are upgrading a 6i report to 9i or higher. This report was dynamically defining desname in
AfterPform trigger as described in <Note:209547.1> How to Change the Report Output File Name Dynamically?
Though the trigger works fine when report is run from the 9i Builder, in 9i Reports Server
(9.0.2.x.x and 9.0.4.x.x) or 10g R2 (10.1.2) desname defined in this trigger does not take effect. Report is
written to the cache but not copied to the location specified by dynamic desname parameter.
Engine trace file shows the following :
[2004/8/12 4:5:38:44] DST 50103 (C Engine) 16:05:38 DST DynamicDes: desname=g:\abhi\delete\ExecOvr20Sec_clerUG-0.PDF desformat=PDF destype=File copies=1 level=Report
[2004/8/12 4:5:38:54] DST 50103 (rwfdt:rwfdtfl_FreeDistList) running
[2004/8/12 4:5:38:64] DST 50103 (rwfdt:rwfdtfl_FreeDistList) quit
[2004/8/12 4:5:38:64] Debug 50103 (EngineImpl:run): CRunReport returns: 0
[2004/8/12 4:5:38:64] Debug 50103 (EngineImpl:run): Quit
This shows that the dynamic location is being READ, but the output file is not being written to the same.
When the desname is hardcoded in the URL, the file is being generated to the location proving that correct
directory permissions are in place.
AfterPform trigger is firing, which can be tested by srw.message commands or by assigning
the desname's value to a field and displaying it in the report. Even if you hardcode the desname
value in afterpform trigger, it does not take effect.
Whereas, desformat value assigned dynamically in same trigger works fine.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document