Data returned by connection "monitor_apps_REST_event" doesn't include all values returned by QRS endpoint ".../qrs/event/full"

[LDR]

Hi everyone,

As usually, I appreciate a lot your time. Thanks for giving me support.

Ok, let me explain what I found and let me know if I'm doing anything wrong.

Via QRS API and using POSTMAN I have queried the endpoint ".../qrs/event/full". QRS API for each trigger inside each reload tasks is returning in JSON format some columns that I want to use. Let me show you (are in yellow background):

Then, in order to retrieve the same data in an app in Qlik Sense, I loaded all  this data using the connection created by the own Qlik and called "monitor_apps_REST_event". At the end this connection queries the same end point that I queried from POSTMAN but using it, I don't see  any of the columns I want to use inside any table that Qlik has loaded.

I'm wondering that QS is omitting some columns like "schemaFilterDescription","incrementDescription" or "incrementOption".

Of course, I wondered as well that maybe my approach is missing something.

Can you tell me how to load the complete set of columns returned by "qrs/event/full" using only Qlik Sense? I wouldn't like to query it outside QS, convert it to csv format and open it from my app in QS again.

Let me share the data model generated by QLIK when I use "monitor_apps_REST_event".

Ah, I created a REST connection as well and the result is the same than with the connection before so in my opinion QLIK is not including all possible columns when read the returning JSON file.

Best regards

[Marc]

Using the Data Load editor 

if you select the connection 'monitor_apps_REST_event' and click 'Select Data', then

tick the Root Table and

insert the default script

if all the columns and tables are selected, and the script is not modified they should be included.

you should find the IncrementDescription & IncrementOption prosperities on the root table

and as the schemaFilterDescription is an array, it gets its own table

NB: if you scroll to the right in the Data Load Editor Preview window you should see the properties you are missing.

You may also want to make sure that the Service Account configured on the Data Connection is a RootAdmin