topic Re: Qlik Sense Rest connection when response gives several tables in Connectivity & Data Prep

Qlik Sense Rest connection when response gives several tables

enfodavid — Wed, 22 Dec 2021 14:19:47 GMT

Is it possible to avoid the problem that an API gives me several tables as a response. When connecting to for example https://api.worldoftanks.eu/wot/encyclopedia/tanks/?application_id=demo as a rest connector I can only get several tables as such

Is there an easy way when loading these to just create a long list of all the entries? Right now it gives me one entry per title. I'm guessing it can be done with a setting when importing the data. I would be able to just load and concatenate all of them but all tables return different fieldnames when requesting them.

Re: Qlik Sense Rest connection when response gives several tables

enfodavid — Thu, 30 Mar 2017 12:55:41 GMT

mto‌ I tried this after watching your youtube video about the star wars rest connector. You said it took some fiddling to get it working, I was just wondering if this is something you've fiddled with

Re: Qlik Sense Rest connection when response gives several tables

Michael_Tarallo — Thu, 30 Mar 2017 16:09:08 GMT

Hi David - thanks for reaching out, let me take a look and I'll get back to you.

Re: Qlik Sense Rest connection when response gives several tables

Michael_Tarallo — Thu, 30 Mar 2017 16:24:34 GMT

Hi David,

This is definitely a strange structure to parse - I also tried this endpoint / resource: https://api.worldoftanks.ru/wot/encyclopedia/vehicles/?application_id=demo - because the one you provided had a note about being deprecated and was hoping they would combine the structure. I am not sure why a single member is created to return a row of data for the same field names. If there isn't a way to adjust the response in the API with provided parameters AND all the field names that come back are the same, then Qlik should automatically concatenate this into one table. Let me know if you would like me to solicit additional help.

When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

Regards,

Michael Tarallo (@mtarallo) | Twitter

Qlik