Problem accessing parameters using the request supplier in Conf 4.1

  • 2
  • Problem
  • Updated 2 years ago
  • Acknowledged
The scenario I'm trying to build for is one where a value will be passed as a querystring parameter in the URL of the Confluence page. The page contains Reporting structures which need to use this value.

In Confluence 3.5 this works like a charm. Here's the markup, which looks for a parameter called "version":
{code}
{report-block}
{local-reporter:request:parameters > @all}
{text-filter:key|value=version}
{local-reporter}
{report-body}
{report-info:request:parameters > version}
{report-body}
{report-empty}No Version parameter found. Do some default action.{report-empty}
{report-block}
{code}

Trying to replicate this in 4.1.4 proved troublesome. Going back to basics, I thought I'd just grab the entire parameters collection and spit it out in a table. I.e. drop the filter temporarily. But at first this gives no results. It's difficult to share the markup from 4.1.4, but the local-reporter line looked like the one above.

Just playing around with the keychain, I took off the > @all part and then at least I got some response, but it's not exactly what I was expecting:

Key : Value
title : [Ljava.lang.String;@3a1181bf
spaceKey : [Ljava.lang.String;@535d4061
version: [Ljava.lang.String;@f2dcb09

The markup giving these outputs is nothing special:

{code}
{report-column:title=Value}
{report-info:entry:value}
{report-column}
{code}

Any assistance greatly received.

Thanks,

Charles
Photo of Charles Hall

Charles Hall

  • 114 Posts
  • 5 Reply Likes
  • looking for an answer!

Posted 6 years ago

  • 2
Photo of Yik Boon Tan

Yik Boon Tan

  • 228 Posts
  • 9 Reply Likes
This appears to be a bug. Created a bug request, https://greenhouse.customware.net/jir.... Feel free to give further details if any.
Photo of Charles Hall

Charles Hall

  • 114 Posts
  • 5 Reply Likes
The bug report has this marked as "resolved" for version 4.0.1 of Reporting. I'm using 4.1.0 and it still seems to be broken (related to my other bug report here: http://community.customware.net/custo....
Photo of Nurhana Ziana Bt. Hanafi

Nurhana Ziana Bt. Hanafi, Employee

  • 3500 Posts
  • 269 Reply Likes
Hello Charles,

This bug is actually fixed on Reporting 4.0.1, however other issue comes out on Reporting 4.1.0. I have logged a report for this bug in our bug tracking system (as described on other thread).

Thanks&Regards,
Ziana
Photo of Charles Hall

Charles Hall

  • 114 Posts
  • 5 Reply Likes
Hi,

Any update on this issue please?

The link you pointed at previously is marked as resolved. We're using Reporting 4.1.0.

Thanks,

Charles
Photo of Nurhana Ziana Bt. Hanafi

Nurhana Ziana Bt. Hanafi, Employee

  • 3500 Posts
  • 269 Reply Likes
Hello Charles,

I believe this issue is related with the Supplier of Reporting plugin. Our developers are working on it now. You may find our latest products on below link: http://community.customware.net/custo...

Thanks&Regards,
Ziana
Photo of Devin Sanders

Devin Sanders

  • 15 Posts
  • 0 Reply Likes
Hello, we're looking for an update on this issue. Seems to still be broken on Reporting 4.3.3. Any news? Thanks
Photo of Nurhana Ziana Bt. Hanafi

Nurhana Ziana Bt. Hanafi, Employee

  • 3500 Posts
  • 269 Reply Likes
Hello Devin,

Currently the bugfix for this is not in our roadmap.

For updates on the fix, you could either watch our Reporting plugin here (click on Watch Add-on on right hand side menus under DETAILS tab): https://marketplace.atlassian.com/plu... or find our plugins' updates here: http://community.servicerocket.com/se...

Thanks&Regards,
Ziana
Photo of Devin Sanders

Devin Sanders

  • 15 Posts
  • 0 Reply Likes
Ziana,

Thanks for the update! I'm disappointed to hear that it's not on the roadmap (especially since you said previously that you were working on it) - fixing this bug would be huge for our organization & the way we use scaffolding & reporting. Please add a vote for us to the ticket. Thanks
Photo of Nurhana Ziana Bt. Hanafi

Nurhana Ziana Bt. Hanafi, Employee

  • 3500 Posts
  • 269 Reply Likes
Hello Devin,

I believe it was dropped due to more urgent issues that time. Anyhow, I will add one vote for you in the ticket.

If you're interested to fix & use it in your local, you could find the Request Supplier source codes here: https://bitbucket.org/servicerocket/s...

Thanks&Regards,
Ziana
Photo of Devin Sanders

Devin Sanders

  • 15 Posts
  • 0 Reply Likes
For others with this issue, you can work around it by creating a user macro & utilizing $req.getParameter(parameter). Here's an example that generates a report-variable macro & sets the value to the value of the given url parameter:

## @param Variable:title=Variable Name|type=string|required=true|desc=Name for the variable to be generated/populated
## @param Parameter:title=Parameter Name|type=string|required=true|desc=Parameter name
#if ($req.getParameter($paramParameter))
<ac:structured-macro ac:name="report-variable"><ac:parameter ac:name="name">$paramVariable</ac:parameter><ac:parameter ac:name="value">$req.getParameter($paramParameter)</ac:parameter><ac:parameter ac:name="atlassian-macro-output-type">BLOCK</ac:parameter><ac:rich-text-body>
<p>&nbsp;</p></ac:rich-text-body></ac:structured-macro>
#else
<ac:structured-macro ac:name="report-variable"><ac:parameter ac:name="name">$paramVariable</ac:parameter><ac:parameter ac:name="value"></ac:parameter><ac:parameter ac:name="atlassian-macro-output-type">BLOCK</ac:parameter><ac:rich-text-body>
Photo of Nurhana Ziana Bt. Hanafi

Nurhana Ziana Bt. Hanafi, Employee

  • 3500 Posts
  • 269 Reply Likes
Thanks for sharing your workaround with us! :-)
Photo of Tue Dissing

Tue Dissing

  • 4 Posts
  • 1 Reply Like
remember to add

#end

at the end of the above scripts. Otherwise it will not work.
Photo of Charles

Charles

  • 6 Posts
  • 0 Reply Likes
This still appears to be an issue in the latest version of Reporting. Any chance it can receive some attention? This seems to be a regressive bug as it worked once upon a time.
Photo of Charles

Charles

  • 6 Posts
  • 0 Reply Likes
Over 5 years since this issue was reported, but still no fix (only a workaround). :(