Skip to Content
Former Member
May 18, 2010 at 12:54 AM

Use of null parameters for opendocument command using AIX BOE server


Good evening guys

I'm having the next problem : My team and I developed a series of reports with Crystal Reports 2008 having a Windows BOE Server. We call these Reports from an external application which displays a series of filters to be selected by the user. Such an application generates URLs depending on the values provided by the user, so an specific URL gets generated depending on the user selection criteria. This URL calls the opendocument command, so the Reports gets executed in the BOE Server. I read that it is possible to pass null values for the parameters the Reports use, just like this


In the opendocument documentation it is clear that it is a valid URL syntax:

You can pass NULL values to a parameter by leaving the right-hand side of the statement blank. For example, prompt0=&prompt1=1000

sets prompt0 to NULL.

In this case, I am sending NULL as value for the parameters lsSP_OPERATIVEUNITID and lsSP_PRODUCTID.

I tested it in the environment I already explained to you (BOE Server = Windows), as a matter of fact, all my reports might need to receive null as a value for their parameters. If I copied this URL and paste into my Internet Explorer it works smoothly.

The problem comes when I try to implement this kind of URL in a AIX BOE Server which (XI 3.1 FixPack 2.7 is installed there).

If I execute this URL in an AIX installation, I keep getting this error: Type mismatch: Unparseable number: "".

If I change the value specified, so none of the parameters are null, then I get the Report to run properly. But I need to use null values as parameters for my reports.

I did not notice in the opendocuent documentation that there's some issue related to null parameters when having an AIX BOE Server. Do you know what this problem might be? some BOE configuration maybe?

Any help will be greatly appreciated.