This is not the usual iQlik post, in which I try to share a particular technique, but it is something I would like to share with you and know what you think about it. I’ve been working with large Apps and I detected a possible feature that would be nice to have on QlikView desktop. I already submitted it on QlikCommunity, so if you would like to vote for it, go ahead, login, and search for the idea under the “QlikView Development” forum.
Here’s what I submitted:
It is becoming more and more common to work with massive data in a QlikView application during development. Typically, if you want to create/modify a large qvw (one that requires XX GBs of RAM) on your local machine using QlikView Desktop, you need to reduce the data so that your computer can handle it. Another option is to Develop directly on the server via Remote Desktop so that you can work with all the data, which is highly convenient so that you can spot trends in your complete data model and identify different scenarios which might not be easily visible when reucing the app. Besides, not always do you have access to the server via Remote Desktop.
The idea: Allow QlikView Desktop to open a local qvw but use server resources for RAM and processor. That way, the Developer will be able to work with all the data, on a local machine, using QlikView Desktop with the remote resources. As opposed to the “Open in Server” feature, you would be able to actually develop on the app, create new objects, change the script, etc.
What do you think?
Mike.
![[VIDEO] Incremental Data Extracts with Qlik using Delta Tags and QVD Segmentation](https://aftersync.com/aftersync.com/wp-content/uploads/2019/05/Delta-Tags-Example-500x383.png)
Hi Mike,
I havent read the discussion on the community yet. so please excuse me if its a repeat.
It seems a good idea but we also need to consider the ramification on network bandwith. For the size of the QVD you are discussing, it may take a lot of time to transfer the file across to the server before any meaning work can be started.
In certain cases, RDP may be a better solution.(?)
I always choose to work with a reduced dataset when working on personal laptop.
Also, looking at the way qlikview is designed, Qliktech seems to move away from collaborative development – for now. Which creates less overhead for them.
But then, i may agree with a feature where ‘Open in Server’ may allow one to make modifications to the document.
Cheers,
Kalyan
Hi! Thanks for taking the time to send your comment.
With everything happening on the server, there would be no need to transfer any files from your computer to the server or vice verse. Also the reason you work on the server is because the app is too big to be handled on a PC, so the QVDs can not be generated on your machine, unless of course you use a reduced dataset. Sometimes, in my own personal opinion, it’s better to work with all the data so that you can, during development, spot trends or patterns you would otherwise not be able to.
Thanks again and have a good day.
Mike.
Nice idea !
I believe that the already mentioned risk of altering the file in server should be addressed by having implemented also a framework allowing development versioning and staging to development-test-approval-production state of each project.
Perhaps even having a integrated management console for projects among the production and testing QV servers…
I have explained some of this concept, of having at least 3 clearstagesof the development, development / testing / production in my blog: http://blog.qqinfo.ro
Sempre fi,
Cotiso | QQinfo
I was thinking the same from a few months. Actually it started when i hear that qv 12 will have a web based development. Don’t know if QT have the same in mind but i’ll be very happy to see it in action
Steafn