CR hyperlink opening in same window, window keeps shrinking

 3 Replies
 0 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
mikeP
Veteran Member
Posts: 151
Veteran Member
    We have a system of 10 reports set up like a mini-web site, the reports link back an forth to one another in a variety of ways. All the reports are published in LBI with "Same window" selected for the Hyperlink Targets setting in the report's Output Options. This is the way we want it, and it works well except for one issue:

    Every time a hyperlink is clicked to invoke another report, the client area in the CR viewer adds another narrow margin, which in effect make the border around the report viewer just a tad wider, and the report viewer a little smaller. I've attachd a small image showing this.

    This has been an issue for the 8-ish years we've been using Lawson, but since I'm migrating a lot of reports to a new provider, I thought I'd ask the question: Is there any way to avoid this other than opening each link in a window?

    Matthew Nye
    Veteran Member
    Posts: 514
    Veteran Member
      how are you links constructed in your reports? Are they FS service calls (FS:RS:RS-PROD?15......) or direct RS URLs (http://rs-server:9080/ers/......)?
      If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
      mikeP
      Veteran Member
      Posts: 151
      Veteran Member
        I've used FS calls, example below. The RS syntax I got working results in a longer url, and I found that they are truncated by LBI at some point, so shorter is better. Thus the cryptically short parm names in the example.

        https://lbiprod.domain.ed...R=N&_E=130031&_S=pal
        Matthew Nye
        Veteran Member
        Posts: 514
        Veteran Member
          what version of RS are you on?

          Im not sure why youre getting this, i imagine its related to the fact that FS is calling RS and since RS is a service within FS, it wants to keep the main container (window) in FS, which applies its CSS properties (this is a just a guess, not based on factual information). If you want to continue down this path, Id say explore the properties of that page with Developer Tools in IE and see where those borders are coming from. You might (thats a big "might") be able to modify a CSS class to eliminate them.

          However, an alternate way to handle this would be using FS modules and the "replace" function. Im not sure of your exact scenario, but Modules can be displayed independent of a dashboard. If you created a module that displayed each of your reports and then modified the links to point to the necessary module, it might get you around this issue while still retaining your features. youll have to do some magic (read: javascript) to pass in your variables but you can probably get it to work.
          If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/