1. 

   Mark, Member

   I'm wondering if there's a way to preserve the GET_[parameters] across report runs. I can send a get parameter that is used by a parameter query to show a valid list of options, but after the report runs, the GET param is no longer part of the URL so parameter query fails and the report doesn't show the data.

   Should I be using some other kind of mechanism? We access the report by direct url.
2. 

   myDBR Team, Key Master

   Can you be more specific on how you want to reude the GET_[parameter] parameter?

   --
   myDBR Team
3. 

   Mark, Member

   Ultimately I'd like to send a list of securityIDs to the report in the url, and have a parameter query in that report use the list of securityIDs to generate a list checkbox list of securities. I can do this initially with using a GET_param, but after the report runs, then GET_param is no longer part of the URL. So subsequent runs causes an error for the parameter query since it no longer has the GET_param from the URL.

   As I said, we do not log into the site with users as we access reports via direct URLs.

   Might there be another way to accomplish sending over securityIDs that persist so the parameter query can use them while the user is running reports?
4. 

   myDBR Team, Key Master

   There are three ways of passing parameters to a report:

   1. Using user changeable parameters ('u')
   2. Using secure parameters ('p') which are included in hash value and that cannot be chamged by the user
   3. Temporaty parameters (GET_*) which are fully dynamic

   In your case, you are better off using user changeable or secure parameters.

   --
   myDBR Team
5. 

   Mark, Member

   Ok. How do get the secure parameters to the parameter query?
6. 

   myDBR Team, Key Master

   See the Direct URL Access to Reports.

   —
   myDBR Team

Reply

You must log in to post.