Prev
Next
Forums Performance Management Lawson Business Intelligence/Reporting/Crystal

Passing parameters to report through url

 3 Replies
 0 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
George Graham
Veteran Member
Posts: 201
Veteran Member
10/23/2013 5:58 PM
    Trying to set up some reports to run as "scheduled" every other week so setting them up in windows task scheduler to submit the URL and create a new instance, I have that working fine, including the login, but the report has parameters - and when I try to pass the parameters in the URL it still brings up the window and asks for them to be filled in. Version of RS is 10.1.

    Here is what is being passed as part of the string: &FiscalYear=2013&AccountingPeriod=4

    Those are the parameters defined in the report - and if those are filled in if the report is scheduled normally it works fine. But can't seem to pass these values in...?
    mikeP
    Veteran Member
    Posts: 151
    Veteran Member
    10/23/2013 6:27 PM
      It's been a while, but I found this in my notes:

      Report formula hyperlink
      When parameters are passed, add &Dobeforeevent=false to the URL to prevent LBI from displaying the parameter entry page,

      Here's an example from a working report's hyperlink to another report:

      formula="https://xxx.xxx.edu:9443/ers/ersRequestHandler.jsp?CMD=VIEW&NewReport=true&Dobeforeevent=false&GroupTree=false&REPORTNAME="


      This parm string is appended to the above to form the final hyperlink:

      formula = {@ServerName} & "4JEI003" & _
      "&_R=L" & _
      "&_E=" & cstr({Command.EMPLOYEE},"#") & _
      "&_S=" & {?_L}




      George Graham
      Veteran Member
      Posts: 201
      Veteran Member
      10/23/2013 10:13 PM
        Thanks mike - that is still prompting for the parameters. But I'm not quite sure - are you also passing parameters in your URL? Is that the second part of your formula?
        George Graham
        Veteran Member
        Posts: 201
        Veteran Member
        10/23/2013 11:06 PM
          Actually the Dobeforeevent=false did the trick - when I reran it I must have fat fingered the URL. After looking at it and figuring that out it ran fine. Thanks again!!