4 Replies Latest reply: May 9, 2016 1:24 PM by Tyler Waterfall RSS

    Duration_min error script in Governance Dashboard 2.0

    Gabriela Martinez

      Dear community,

       

      I am working with the governance dashboard and sometimes when I reload the app, I get this message error:

       

      Script line error:

      Let duration_min   = ceil((peek('SessionTimeStamp',0,0'tmp_incrementalConcurrency')-42471.418344907)/-/60/24)

       

      I have not found any documentation that could be useful in this issue. Does anyone know how to fix this?

       

      Thanks and best regards!

        • Re: Duration_min error script in Governance Dashboard 2.0
          Peter Cammaert

          The cause of this problem can be found by debugging the script, just like in any other QlikView document.

           

          Script line error:

          Let duration_min  = ceil((peek('SessionTimeStamp',0,0'tmp_incrementalConcurrency')-42471.418344907)/-/60/24)

           

          Apparently, variable sessStart is undefined, resulting in a single minus sign between two slashes. That's an illegal expression in QlikView script.

          The error location is line 29 in (hidden) script tab  SessionConcurrency.

          The line where sessStart is (not) set is line 28.

           

          As I don't have your environment at my disposal, I cannot replay what is happening during a reload at your place.

           

          Best,

           

          Peter

          • Re: Duration_min error script in Governance Dashboard 2.0
            Tyler Waterfall

            I know this has been marked resolved, but are you still seeing this?

             

            I am curious if you saw this initially when reloading via QMC (Publisher)?

            It is related to the field "Session Concurrency Interval" which is set to "Always one selected value" but is sometimes unselected somehow when the app is reloaded in QMC.

            The way to check is to look at the app in Access Point after it reloaded and check the "Session Concurrency Interval" value selected on the Configuration page. (You might need to "Always show" the configuration page by clicking that setting on the "Scan Details" page of the app.). If there is no Session Concurrency Interval value selected, then you have encountered this issue.

             

            Please let us know if you see this behavior!

            Thanks!

            Tyler