Pass parameters to a Visualization from a different report page

[Erin Trotter]

Hello everyone.  I am looking for a way to pass a parameter to a report page from within another page.  So, I have an HTML page made in App Studio and it has a subdivision parameter.  Then I have a visualization page for something else, but it also can take in a subdivision parameter (it also has a parameter selection box on the visualization page)...   However, I want to add a button to the page in App Studio that will open the visualization and have the subdivision that was selected on the HTML page, also be selected on the visualization page when it opens.  I am using WebFocus 8.207 though, is it possible?  I have tried adding the parameter to the end of the URL for the visualization like ?&SUBDIVISION = XXXX, but I get an error saying:

Error

Path contains filtering characters not accepted by IBFS action

 

 

 

I tried without the question mark, and the page loads, but the filter is not selected.

[David Beagan]

Coincidentally, I was just starting to do something very similar to this. My solution works in my WebFOCUS 9.1.0. Essentially it passes the parameter as part of the calling URL, just like you tried. However, I did it indirectly with a fex that has an -HTMLFORM with an HTML <form>. 

The URL was something like this:

http://servername:8080/ibi_apps/run.bip?BIP_REQUEST_TYPE=BIP_RUN&BIP_folder=IBFS:/WFC/Repository/workspace_01/&BIP_item=vizual_01&SUBDIVISION=1 

Maybe this doesn't work in WebFOCUS 8.2.07, or maybe you formed your URL differently.

[Erin Trotter]

My url looks very similar to this.  same format... and it opens the item, but without applying the parameter...   Just curious, does the resulting URL also have a selectable parameter on the actual

page for the Subdivision, for example?

[David Beagan]

Yes, I think so. In mine the value in the URL gets selected when the Designer page starts up, and the content on the page is filtered based on that selection.

[Erin Trotter]

I got it working now just the way you said.  The parameter was slightly differently named that in the calling page, so I had to make a modification, but now it works just like you said.  Thank you so much!

[David Beagan]

Funny, once you know it's possible, then you figure it out. 

I'm glad you got it working.