Skip to main content
Solved

Qlik Reports

  • June 3, 2025
  • 1 reply
  • 19 views

Hi everyone,

I’m exploring ways to automate the import of Qlik reports (or datasets exported from Qlik Sense) into Ataccama’s data management platform using API-based workflows. My goal is to ensure that reference data or analytical results generated in Qlik can be seamlessly ingested into Ataccama for further processing, enrichment, or distribution to downstream systems.

From what I understand, Qlik offers REST APIs for data export and integration, while Ataccama provides robust APIs for job execution and data ingestion. However, I’m looking for practical advice or examples on how to best orchestrate this integration—specifically:

  • What is the recommended approach to export data from Qlik (e.g., via Qlik’s REST API or by generating CSV/Excel files from the load script) and then import it into Ataccama using its API?

  • Are there any existing patterns, connectors, or scripts that community members have used to automate this process?

  • How do you handle data validation, error handling, or scheduling between Qlik and Ataccama in such a pipeline?

Any insights, code snippets, or best practices would be greatly appreciated!

Best answer by rafeeq.durowoju

Hey ​@onufry I hope I can partially answer some of these questions.

What is the recommended approach to export data from Qlik (e.g., via Qlik’s REST API or by generating CSV/Excel files from the load script) and then import it into Ataccama using its API?

Personally I do recommend generating CSV/Excel files and then importing into Ataccama using its API as this allows you to manage the load on Ataccama by potentially batching the reads from a file, with a direct application to application integration, it makes it harder to maintain the load. 

Are there any existing patterns, connectors, or scripts that community members have used to automate this process?

I would look at some integration questions posted in the community such as this one which might help inspire your integration: 

https://community.ataccama.com/data-quality-catalog-94/alation-integration-531?tid=531&fid=94

 

How do you handle data validation, error handling, or scheduling between Qlik and Ataccama in such a pipeline?

Data validation and error handling would most likely be a trial and error process during the building of your integration. In terms of scheduling, you can promote your integration as a workflow and put a scheduler to run the workflow on a regular basis. You can also leverage third party schedulers to trigger the process. 

View original
Did this topic help you find an answer to your question?

Forum|alt.badge.img+3

Hey ​@onufry I hope I can partially answer some of these questions.

What is the recommended approach to export data from Qlik (e.g., via Qlik’s REST API or by generating CSV/Excel files from the load script) and then import it into Ataccama using its API?

Personally I do recommend generating CSV/Excel files and then importing into Ataccama using its API as this allows you to manage the load on Ataccama by potentially batching the reads from a file, with a direct application to application integration, it makes it harder to maintain the load. 

Are there any existing patterns, connectors, or scripts that community members have used to automate this process?

I would look at some integration questions posted in the community such as this one which might help inspire your integration: 

https://community.ataccama.com/data-quality-catalog-94/alation-integration-531?tid=531&fid=94

 

How do you handle data validation, error handling, or scheduling between Qlik and Ataccama in such a pipeline?

Data validation and error handling would most likely be a trial and error process during the building of your integration. In terms of scheduling, you can promote your integration as a workflow and put a scheduler to run the workflow on a regular basis. You can also leverage third party schedulers to trigger the process. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings