Allow column variable to be passed into Link to URL formatter when using Custom Parameters

Larry Beasley shared this idea 3 weeks ago
Completed

When using Custom Parameters, trying to also pass the column value by adding ## does ot work. Perhaps that's a caveat to using custom parameters, you cannot also pass in the column value.

Comments (3)

photo
2

Hi Larry,

Thanks for reaching out. This is indeed a current limitation.

/AAAAANQaQgzAEtuNHwAAAABqDSEGYIntxg8AAAAAtYYQA7DEduO3bX19HQAAAMCfECEGUINshwgAAAAAUGsIMQBLbDd+AAAAAKg1hBiAJbYbPwAAAADUGkIMwBLbjR8AAAAAag0hBmCJ7cYPAAAAALWGEAOwxHbjBwAAAIBaQ4gBWGK78QMAAABArSHEACyx3fgBAAAAoNYQYgCW2G78AAAAAFBrCDEAS2w3fgAAAACoNf8fuptvL1toNasAAAAASUVORK5CYII=

/K+5N9ijywqUAAAAASUVORK5CYII=

Doesn't pass in column value (##)

/AaMSkjqXNYKYAAAAAElFTkSuQmCC

Whereas this does:

/pyeJ3XiBs+AAAAABJRU5ErkJggg==

/AAAAAElFTkSuQmCC

As such, I've gone ahead and logged an enhancement request for this.

Any potential updates regarding this will be posted here.

Regards,

Mike

photo
1

Hi Mike,


I don't know if this was just a bug that got resolved but I just got confirmation that this works:

https://${URL_PARAM}/myfolder/asp_service.asp?value=##


The parameter in your example should not have the place marker ##. That should be added at report level.

https://${TESTPARAM}/##


Also, other report writers had issues because they added

https://
to the parameter when in fact, that should be added at report level as you demonstrated.


If you can confirm that what I said is true then IMO this idea can be closed and the wiki should be updated to display your tutorial.


Thanks again!

photo
1

Hi Larry,

That makes sense, and I can confirm this. I've gone ahead and reached out to the appropriate contact to update our Wiki entry on this and will go ahead and close this Idea out. Thanks for getting back to us on this.

Regards, Mike