2 Replies Latest reply: Dec 7, 2017 1:22 PM by Brent Nichol RSS

    How can users save their own Visualisation on a published Report

    Erwin Warrinnier

      In many businesses there are "Fixed" and "User Analizable" reports.

      The last ones are mainly reports that are published in a standard form with a general visualisation (eg graphics etc) by QVS.

      They can be accessed by many employees (Qlikview users) that view these reports & change the visualisation to cope with their specific needs.

      My question: is there a way for every user to save their changed visualisation back into the original report ?
      ==> Qlikview must therefor allow a possibility to save back into the published report
      ==> It also must allow  (ad-hoc) user linked configurations into the published report

      Or should you work in another way? (Eg publish data and not a report)

        • Re: How can users save their own Visualisation on a published Report
          Peter Cammaert

          My answer: users cannot do this themselves. A developer must do this, copy for example Server Objects about which everybody agrees that they are worthwhile into the QVW base document, and make them fixed and visisble to all.


          If you mean: can users create their own visualisations and "add" them to a published document, then the answers is Yes!. Have a look into Server Collaboration. These visualisations will not really be added to the document but kept on the server and combined with the objects in the document the moment it is opened in the AccessPoint.



          • Re: How can users save their own Visualisation on a published Report
            Brent Nichol

            Hi Erwin,


            As Perter mentioned, there are a couple of options.


            We normally allow user collaboration on all documents.  Users create objects, sheets, bookmarks and reports for their use, or share will limited or all other users.


            If a set of user created objects are wanted as core components, users can request these objects get copied to the document by a developer.  They will be validated and processed through the change management procedure.


            We have found this provides optimal flexibility, while maintaining tested and stable functionality.


            I hope this helps,