Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello !
I have a suggestion for Qlik Tech itself :
Write MINI Tutorials on the latest features that have been implemented on QV.
IMHO there has been great improvements on the product itself but, we here as customers at the end point, haven't been able to understand/use it all.
Say for instance SET ANALYSIS and now the great improvements on version 9.
So, for some of those features, there should be way way more explanations than only the What's new and reference handbooks.
Something more "piece of cake" !
Anyway, just wanna put this suggestion.
Better than that all would be to have A BOOK about QV, such as THE QV BIBLE or something alike, explaining the history of the product, the CONCEPTS underneath, exploring data model desing techniques, then presentation techniques, BI CONCEPTS as well and so forth.
Great product, I love it.
But wanna KNOW it all !
Thanks !
While the existing expansive documentation for v9 has a tremendous amount of information and the syntax for every function , it would be nice to see more examples of the functions described. I have looked for other books, but have found nothing other than blogs, forums and Qlikview materials. As others have said Qlikview is easy once you know what you are doing.
Good idea ... samples give a better idea of the functionalities available ...
Seeing how its used and what it can do ...
Yeah !
You know, there is a 'WHAT'S NEW IN VERSION 9' QlikView Document. But it's very big !
My idea is something simpler. Like this :
At least for me this would be very very helpful.
As a matter of fact I have a folder there where I store those kind of applications. Have a bunch of them. But they are silly things such as one little application where I have all the script functions tested, another little application showing how to load inline data from csv files. Another application with a simple pivot table. And stuff like that. Whenever I need some of those features on a BIG application of mine, I go into this folder an search for something little where I have the feature I need. Then I cut/paste. It's very useful. Other good point is that you can TEST the feature OUTSIDE your main application, using this little application. Because your original application is usually way , way more complex.
Another thing that I'd like AS A CUSTOMER is to receive a daily email with a Qlik View lesson about some feature or technique. Kind of a Tip of the Day but via email.
So, one QV lesson per day. Those little applications that I told above could come attached on these emails. We would subscribe to the mailing list.
It would be very practical.
ONE LITTLE QV LESSON PER DAY WILL MAKE YOU A QV MASTER ANYWAY !
Hope you like the ideas ! QlikTech ? Are you hearing us ? Do it for us, will you ? Just kidding !
Thanks you all. This is a Great Product and Great Community !
See ya !
Adriano wrote:As a matter of fact I have a folder there where I store those kind of applications. Have a bunch of them. But they are silly things such as one little application where I have all the script functions tested, another little application showing how to load inline data from csv files. Another application with a simple pivot table. And stuff like that.
I've developed a library of small examples like that as well. In my case, I just save every example I post on the forum, as well as a few additional ones created while solving my own problems. An official QlikTech library of little examples might be nice.
Ditto! Still haven't found much -- 6 months later!
Good idea, Adriano
"espero que la espera no desespere"
Thank you !
In my case I keep all my scripts OUTSIDE the QVW file. My QVW only has a single include as their script :
$(Include=TEST131.QVS)
Then I can easily "grep" amongst all my QVWs to search some example of CROSSTABLE for instance.
However, I can not do the same for the visual part. If only I could somehow export the visual part (interface) as a XML, then that could be feasible as well.
Anyway, thank you all for supporting my idea !
BTW, here's a sample application just showing how to use a CROSSTABLE. It's a kit ready for prototyping. I always like to prototype a simple example (subset) of the whole application OUTSIDE the big project. Then, when it's working and reliable I insert it into the original (big) project.
Thanks !
Hi Adriano
I would probably only keep a copy of the script for searching through them because the include will take out the built in script support features?
You can export your document settings as xml. How good this works with grep is however another question.
Juerg
Boa ideia Adriano!
Sería genial poder practicar con ejemplos concretos.