Crystal XI: New Stored Procedure Input Parameter

[N11689]

We have just started testing Crystal XI. We are currently using Crystal 9.

Our reports execute stored procedures via an OLE DB connection to SQL Server.

I am testing adding a new input parameter to a report stored procedure. I have added the input parameter to the stored procedure. I opened the report in Crystal XI and seleced set Datasource Location. When I clicked Update to update to the new stored procedure, I am prompted for the input parameters. I notice that the new parameter is not there. If I enter values into the exiting parameters and click OK, I get a Database Connector Error stating that the procedure expects the new input parameter which was not supplied.

In Crystal 9, when I set datasource location and click update, my new input parameter is automatically picked up.

I can't seem to get Crystal XI to find my new input parameter.

Has anyone experienced this? Although the parameter screen has changed, I don't see any documentation stating that adding a parameter has changed.

Please help. Thank you.

 

[N11689]

Some more information...

I 'profiled' the Set Datasource Location and the procedure
sp_procedure_params_rowset IS picking up the new parameter, however, when the Enter Values screen comes up (in Crystal Reports XI) after I click Update on the Set Datasource Location Screen, the new parameter is NOT there.

Why? What is happening to that parameter where Crystal XI is not recognizing it in the report? If you need more information to help me, I can provided it.

Thank you.

 

[vidru]

Curious behavior, indeed. Could be a bug.

What's the datatype of the parameter in the stored procedure?

If you start a new report (in XI) using the procedure as the data source, do you see the parameter?

-dave

 

[N11689]

The datatype is a char(1).

And, yes, if I create a brand new report and add the stored procedure to the report, that new parameter IS there.

I haven't seen anything in the Business Objects Knowledge base that this has been reported.

Have you experienced this problem?

 

[vidru]

No, I haven't, but I'm using CR 10 presently. I just ran a test, and didn't have that problem. I did have to do a Verify on the report before it picked up a field that I'd added in the 'new' procedure.

If I get some time (not likely today), I'll re-install the CR XI eval and do some more testing.

-dave