Introducing Chris Deniziak, Data and Analytics Architect at CPS, and the newest addition to our team. Below he shares his thoughts on a topic he is very familiar with: Qlik Sense.
As a Qlik developer who started with QlikView, I thought there were a lot of features that had been lost with the original Qlik Sense 1.0 release. Even going to 2.0, it was still lacking a lot from a customization point of view. Since then, which has been about three and a half years, there have been many improvements to the original platform as it was conceived. At this point, I think all those features have made their way back, whether it be out of the box functionality or extensions developed within the Qlik community. This is extremely exciting! Why am I bringing this up? Qlik Sense has come a long way, and with the latest February release, there are a few noteworthy items that bring it up to par with QlikView.
If you’re an "in the data trenches" type of person, you’ll be more than happy to learn that you can now load dynamically from a URL without having to enable Legacy mode. This is huge. I know that my dynamic development had been stifled by having to use a Library or enable Legacy mode when extracting from URLs. Now, as a developer, you can create content, and your administrators will be overjoyed that someone isn’t coming to them and asking for Legacy mode to be enabled so they can use a script they had written in QlikView.
If dynamic URLs were holding you back from converting over to Qlik Sense, now you have no reasons not to. Overall, Qlik Sense is now the better of the two products. If you don’t believe me, give it a shot and download it for yourself! Feel free to share your comments below or send a request to email@example.com to request more information.