Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Now accepting applications for the Qlik Luminary and Partner Ambassador Programs: Apply by July 6!
cancel
Showing results for 
Search instead for 
Did you mean: 
Skage
Partner - Creator
Partner - Creator

Looking for Best Practise regarding loading data from an GraphQL-api via REST connector

Hi all.
I'm looking for some suggestions/advise on how to extract data from an GraphQL api where the data needs to be explored and adapted during development.

The flexibility of the api is making it extremely difficult to iterate since the script most likely will be generated differently each time the query is altered. I'd like to stay away from attempting to write everything by hand.

My strategy, when working with regular REST api:s, is to keep each script untouched, save all tables with the names the script generated, and do the joins and renaming in the transform script.

This works but once the iterations start, I have a hard time aligning the old and the new names and structures. This is a huge api and I'm tackling the most complex part of it with paging and "cost" constraints for the queries.

So, the strength of GraphQL when it comes to frontend development and flexibility make it a nightmare to work with in Qlik.

Working with the current rather dx-unfriendly REST connector can be a challenge at times, but this is at a completely different level.

Any suggestion to keep me sane are appreciated! 
/lars

Labels (4)
0 Replies