2 Replies Latest reply: Feb 19, 2015 1:27 PM by Miguel Catalão RSS

    Qlikview with .NET

    jeremias oro

      Hello to all, im new in qlikview. I've been studying for a couple of weeks and i've completed a few books with exercises.

      I need to do an application where the user can interact with the values. I know i can do it with the INPUT FIELDS but there are a lot of problems with input fields if you want to make a lots of blank spaces where the user will change the values.

      In the company where i work they suggested that i should use .net to create applications and import these with the qlikview to create something similar to the input fields but better, but i dont have any idea about .net and his use. Anyone has used .NET with qlikview? I see that there are a lot of options of different aplications and i dont understaund it at all. What program should i use, or what kind of app i should do?


      Thank you all, and sory for my poor english.



        • Re: Qlikview with .NET



          I am also sailing in the same boat and came across this link JsDoc Reference - Getting Started.


          What I understand from the forums is that. To integrate .NET with qlikview, we need to have Qlik Workbench. Already created QVW can be consumed into .NET application with the help of above link.


          Experts -- Please correct me, If I am wrong at my understanding.




            • Re: Qlikview with .NET
              Miguel Catalão


              You can have different approaches to integrate Qlikview and .Net.


              If you want a seamless integration within both applications the best approach will be using workbench. This integration will allow you to control objects from Qlikview in the .net application, and use these objects directly in the application and manipulate them. The objects will work as part of the .net app.


              You can also embed the qlikview Ajax client into your .net application with an iframe. This approach will allow you to see your Qlikview document (or a single object, from 11.2 up) in the application, but integration is more limited. You can pass parameters to your application, select different documents, and Qlikview allows you to integrate authentication between the 2 applications in order to achieve Single sign on.


              To interact directly with Qlikview values, the source of the data must be altered, and then a reload must be done (unless you use Direct Discovery). The usage of input values, and odbc in macros to create inserting forms is difficult and problematic, and has very high maintenance costs. We already found some issues, like input fields data lost due to Document refreshes, and above all, with very big documents, and slow reload times, users have long wait times, to see results altered in Qllikview.


              Our approach to this was to create .net web forms, accessible from the Qlikview applications. However, depending on your architecture, there are Authentication considerations from the .net application to Qlikview and backwards.


              I hope this gives you some ideas.



              Miguel Catalão