I'm using Qlik Cloud Data Integration (QCDI) and I have to duplicate the same project multiple times for multiple sources.
I exported one project and I am changing the information in order to import all these projects afterward and save time.
But there is one information I need to find and not so easy to find. It is the source connexion ID. For now, I need to create the connection, then create a project with an empty task and finally export the project to have this ID. Is there a way easier to find it.
It feels logical to me that Qlik ought to include "ID" in the list of connections under /data-integration/connections/all
Until then, I suspect that the best solution may be to setup a dummy project using the ID You're intending to switch to, then Export that, rip out the connection section from the JSON and paste it into your existing JSON ready for import.
It's not intuitive and it's not efficient, but it is what it is.
On import via the UI - you can select the new connection at import time. Any new connection can be re-assigned. This means you don't need to manually assign / capture the ID. If you are programmatically trying to adjust your json, there are API's to get connection lists that can also be used - https://qlik.dev/apis/rest/data-connections/#get-v1-data-connections
Additionally, we just released integration with Version Control (GitHub specifically) and a set of Export/Import API's. This adjusts the project export when using VC or the API to a more granular set of objects but also includes a BINDINGS file which can be used to align resources that may change throughout different environments. These API's are documented here - https://qlik.dev/apis/rest/di-projects/. Export a Project Import a Project
Get Export Variables and Update Export variables allow you to programmatically assign the bindings (like connection ID or target database / schema for each task )
@Andrew_ENT - would like to chat about the need for the ID in the UI - if that makes your deployment lifecycle easier - to understand the use case.
I was able to get it working this morning. It still felt a little fiddly, but I've been able to write some notes so that hopefully next time it will be a bit smoother.
