Pass Parameter To Deteils Report, Using Url Deployment Method

[UweTecht]

Hi,

 

I've created a details report "Project Details". In preview the system asks me to input parameter. A soon as I type in the parameter and click apply, the result is as I expect it to be.

 

BUT: Giving the same parameter via URL (f.e. "?pid=2"), the system doen't answer in the expected way.

 

Example:

deployment URL is: http://eu1.caspio.com/dp.asp?AppKey=54ac3000213663dc7f704ca39391

If I open this URL the result is the first entry (pid=1)

BUT: if I try to use "http://eu1.caspio.com/dp.asp?AppKey=54ac3000213663dc7f704ca39391?pid=2" the result is still the same, the system doesn't bring the second entry of the table, still the first one.

 

Can someone tell me what I did wrong?

 

Uwe

[Jan]

Hi Uwe,

 

 

It seems, I found the reason.

The correct URL is

http://eu1.caspio.com/dp.asp?AppKey=54ac3000213663dc7f704ca39391&pid=2

 

Only one "?" is allowed in the URl, it begins the list of parameters. Between parameters "&" is used instead of "?".

 

I hope, it helps.

[Jan]

Hi Uwe,

 

Please make sure that on the "Search Type" step, the "Bridge and external parameters" Radio button is checked.

 

As far as I know, via URL external parameters are passed, so if the "Bridge parameters only" Radio button is checked, the system ignores external parameters.

 

I hope, it helps.

[UweTecht]

Hi Jan,

 

thank you for your answer. Didn't help because on the page "Search and Report Wizard - Search Type" I have checked the correct option "Bridge and external parameters".

 

Any other suggestions?

 

Thanks again!

[Jan]

Hi Uwe,

 

Please make sure that on the "Configure Filtering Fields" step, in the "Value" field, the parameter "[@pid]" is used. The uppercase letter can be the cause of the problem.

[UweTecht]

Hi Jan,

 

thanks again. I did as you suggested. Result is still the same.

 

Kind regards,

Uwe

[UweTecht]

Hi Jan, indeed! Thanks!

Uwe

[navyareddy]

It's not exactly a solution, but you can take advantage of the fact that sandboxes use the same IDs for fields. Create the field in production and then create a new sandbox. You'll then be able to reference the id for the field in the sandbox without worrying that it'll break once it's deployed. This assumes that you'll need to dynamically pass in the field to the report.

If however, you don't need to dynamically pass in the field to the report, just the filter parameter, just setup the report so it already has the field in place for the first filter and leave the filter value blank. Then you'll only need to pass in the value to the report and you avoid the whole ID issue in the first place.

Of course, if you're willing to go the extra mile, you could use the List call of the metadata api to get the IDs of the Fields programmatically. Then you need to post deploy update the IDs with the correct values for the field you're working with. You can do this with ANT or the Metadata API.

[cheonsa]

Hello!

For more details about passing parameters via query string, you may check this article:

https://howto.caspio.com/parameters/parameters-as-query-string-values/