User Parameter Value is Not Passed As Null In Correct Place to CGICMD.dat File When Being Passed Directly from URL
(Doc ID 472320.1)
Last updated on AUGUST 06, 2020
Applies to:Oracle Reports Developer - Version 10.1.2.0.0 to 10.1.2.0.0 [Release 10gr2]
Information in this document applies to any platform.
This problem can occur on any platform.
This happens when using Cgicmd.dat file.
Using cgicmd.dat to run a report with parameters on the web. For example, you have a report sample.rdf with two parameters, P_1 and P_2. The cgicmd.dat entry for your report is as follows:
You attempt to run the report without a parameter form by passing in the values directly to cgicmd.dat using the following URL:
In this case, the report will be run using P_1=10 and P_2=20, since that is the order of the values being passed in the URL.
If you try to run report with a null value for P_1 using following URL:
Then you expect it to pass value 20 to parameter P_2 and let P_1 be null. However, the P_1 parameter "gets" the value "20" in this case. You want to be able to pass in a null value in the correct order directly from URL.
This is not an issue when passing in values (null or otherwise) directly into parameter form, using paramform=yes and omitting the parameters from cgicmd.dat entry.
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