For my case I would like to pass system tokens [user:user_id] thru the forena report bean.
I created a parameter in the bean to accept tokens and replace the $parms with the tokens.

CommentFileSizeAuthor
#3 screenshot.png13.48 KBtomhung
#2 bean_token_url_parameter-2616766-0.patch1.29 KBtomhung
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tomhung created an issue. See original summary.

tomhung’s picture

tomhung CreditAttribution: tomhung commented
FileSize
bean_token_url_parameter-2616766-0.patch1.29 KB
tomhung’s picture

tomhung CreditAttribution: tomhung commented
FileSize
screenshot.png13.48 KB
metzlerd’s picture

metzlerd CreditAttribution: metzlerd commented
Status: Active » Needs work

This patch does not cleanly apply to git checkout. It seems to have trailing whitespace errors as well as a corrupt patch at line 24 error.

dcrellen’s picture

dcrellen CreditAttribution: dcrellen commented

I think my question is related to this URL args issue.

I am attempting to use Beans to send my Forena report a ‘NID' parameter to process my query which returns an 'overall_score' result which I then incorporate into the overall display for that node. In the Forena Bean I check ‘Use menu parameters from url’. To test, I manually enter and tack ‘?nid=48’ onto the page’s address line (I use clean URLs where the title is aliased to the address, i.e., xxx.com/aspen-house') so my address becomes 'xxx.com/aspen-house?nid=48' which works as expected.

I then put a fixed URL Parameter into the bean, for example, ‘nid=48’ which also gets the correct response. So I know this setup will work if I can make the parameter a variable as in tomhung’s screenshot. But of course I don’t have the ‘Allow tokens in URL Paramerts’ checkbox. Is this patch still available and is it what I need to solve the problem? I am not a programmer so would not know how to do the patch but if this issue is still being worked on I can probably wait for a released implementation as I have a temporary hack workaround.

I have been able to accomplish a workaround solution using Forena with Feeds. It's a fallback solution, however, because it requires manual intervention (or a possible periodic feeds update). My query is rather complex in that I need to weigh several factors from 3 separate content types to arrive at an overall rating score for each of hundreds of properties. My goal is to dynamically display this score when a specific property is viewed. Since the rating could change based upon additions or deletions of some of the inputs I need to rerun the query for the affected property. This does not warrant frequent rerunning the Feeds for the entire property base, however.

I am once again overwhelmed with the quality of Dave's Forena Reports and the breadth and depth of his videos and I look forward to doing a lot more with the module. And now with the Bean interface we can use Forena’s report writer to easily handle far more complex database work than using Views.

I am using Forena 7.x-4.9 and Bean 7.x-1.11