Understanding and monitoring changes to the various Qlik Sense API's
Qlik Sense is an unusual piece of software when it comes to its APIs; while most software and platforms may have up to 3 different APIs on the higher end to take care of things, Qlik Sense boasts a mind-boggling 20 APIs, which includes the 10 “sub-APIs” under the Capability API. This is amazing for developers, as this means almost anything can be controlled one way or another while cooking up your next extension, mashup, widget, or even a totally standalone .NET application.
However, this now means that there are 20 different APIs to keep track of between versions, which is approximately as difficult as herding a couple dozen cats into the same room at the same time. Qlik Sense is constantly updating, and it can become a nightmare to keep up to date on everything if you’re keeping up with more than a handful of different customizations. It becomes even more challenging if something breaks between versions and you’re not exactly sure why.
So how do we keep track of these updates? API change notes aren’t usually included with the release notes of each new version, and it can become tiresome to check each individual API’s help page for differences.
The guys and gals at Qlik Branch have thought about this, and recently released Qlik Sense API Insights!( https://api-insights.qlik.com/) With API Insights, we’re now able to actually visualize changes in between versions (starting with version 3.2), from a general overview level, showing at a glance how many things were changed and where, all the way down to which particular functions were added/updated/deprecated/removed from which API. We can also see a quick overview of which APIs/functions a particular Qlik Sense version supports if you’re targeting a specific version. For more information and details on how to utilize the app, you can visit the blog post announcing the release here.( https://branch-blog.qlik.com/qlik-sense-api-insights-3e84b61602bd)
One thing to note is that when viewing the overview of changes and update details, “Baseline” refers to the older version and “Target” refers to the newer version that you would like to compare against. If you select a newer version for “Baseline”, API changes may show incorrect or reversed, such as new API functions showing as removed.
Have a new project or custom functionality you're looking to explore? Contact us today and let us put our expertise to work and bring that new idea to life!