If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Stored Procedure Parameter Prompt

Started by pyovich, 06 Mar 2014 04:37:25 PM

Previous topic - Next topic

pyovich

Moved from Framework:

I have a stored procedure that requires a date prompt for it's result set (endDate).  In a custom prompt page on my report,  I have a Date Prompt component that references the parameter in the stored procedure (yes, the parameter is named the same as what is being requested in the stored proc).  When the report is executed, an auto-generated prompt screen is display is shown asking for a value for endDate.  After receiving its value, my custom prompt page is displayed.

When I set the value for the parameter in the auto-generated prompt page the shows up, the value is carried over to my custom prompt page, so the parameter is getting populated in the first screen. 

Quesetion: What am I missing that would make that first/auto-generated prompt displayed when the custom page is really what I want?

Much obliged.

-Peter


Lynn

Do you have a default date set up for the procedure in FM? It has been a while since stored procedures were inflicted upon me but I vaguely recall something to do with defaults.

pyovich

This is what I have for the Value on the argument: #prompt('endDate', 'date', $current_date)# 

I added the $current_date default but the errant prompt is still coming up.

MFGF

Quote from: pyovich on 07 Mar 2014 11:08:11 AM
This is what I have for the Value on the argument: #prompt('endDate', 'date', $current_date)# 

I added the $current_date default but the errant prompt is still coming up.

I don't think $current_date is a valid session parameter. Can you try:

#prompt('endDate', 'date', $current_timestamp)# 

MF.
Meep!

pyovich

Thanks MFGF, that seems to have done the trick.