See what WITH CONNECTION can do for you when working with REST data sources
I was approached by a colleague with a simple but recurrent question, how can I use for…while loops in conjunction with the REST connector, and how can we make it work with the connection library that comes with Qlik Sense.
A few months ago I shared a “hack” so we can do loops in our scripts as we do with QlikView, activating Legacy Mode will make connection library optional, please remember that there are a bunch of good reasons for not do that. “With connection” is a great solution for those of you who don’t want or just can’t activate Qlik Sense Desktop to work in Legacy Mode but still need to loop through several URLs to get complete data.
Let’s do a quick example.
We need to load data from an online data source, we have a URL to connect to the data that contains the ID of each one of the elements that we would like to load into our app.
We have a list of 100 alphanumeric elementIDs and we need to make sure we load them all. Using our REST connector, we could easily connect to the online data source and extract the data, but we faced the issue of how to make to connection loop trough a series of items.
In our example we have an inline table that contains each one of the ID numbers of the elements we want to read in the REST connector, and we need to pass that parameter to the connection URL below.
LIB CONNECT TO 'REST';
Load * inline [
for j = 0 to 99
Let vElementID = peek('ElementID', $(j), 'Teams');
FROM JSON (wrap on) "root" PK "__KEY_root"
WITH CONNECTION(Url "https://www.domain.com/element?key=$(vElementID)/more_stuff/");
DROP TABLE RestConnectorMasterTable;
After the inline statement, we loop over the REST connection 100 times, one time for each row of the inline table, I know we have 100 rows so I'm hard coding that number but if you don't know how long your table is you should check that before and store it in a variable.
Lately, using "With Connection" we have access to the data source URL so we can expand my variable "vElementID" containing the necessary ID for the connection to work.