Will follow this thread to see if anybody responds with an answer, i am also looking for the same.
There is an option to copy data pool from Prod to Sandbox(QA), but that option depends on your license. Here you can pick which data models to copy. Not sure if it copies all the schedules, data jobs, data models, logs, etc.,
Thanks
Muthappan
The solution @muthappan.alaga provides is indeed the easiest way to do so.
For both Data Pools and Studio Packages, the option 'Copy to' should be available. For Data Pools, this might give you some errors for Data Connections that you then have to reconfigure, so be aware of this.
If this option isn't possible for you (which might be case if your environments are on different realms (such as eu-1 and eu-5), the Celonis Content CLI is your only option. With a set of Python commands you can transfer all content you want.
Will follow this thread to see if anybody responds with an answer, i am also looking for the same.
There is an option to copy data pool from Prod to Sandbox(QA), but that option depends on your license. Here you can pick which data models to copy. Not sure if it copies all the schedules, data jobs, data models, logs, etc.,
Thanks
Muthappan
Hi,
To give additional info on that. I have copied the data between PROD and QA using "Copy to" option shown by you above.
As Jan-Peter mentioned in the post below I had to reconfigure data connections but that was easy fix.
"Copy to" option does copy all the schedules, data jobs, and data models.
It does not copy logs. Any data uploaded using flat files also is not copied so it needs to be uploaded manually.
It does not copy any data that was extracted to PROD env. But that was pretty obvious seeing that QA env has a lot less space than PROD, and either way if you are planing on using QA you will use it to test Jobs with sampled data.
As for the entire process of running all copied Jobs in QA env it can get a bit messy but it depends on the quality of transformation scripts that you have. The less weird junk you have the more easier it will be and you won't have to waste time on figuring out why some stuff is working on production but is crashing in QA.
Overall, I found it to be a good way to figure out the things that I have inherited from previous team members.