I would like to have differential check as the initial step in environment transfer, and from that step get a selection of objects I would like to transfer. In my opinion one should not transfer objects still in development to the production environment, which one is forced to do in the current setup.
The production environment should be a clean production environment!
Selective environment transfer would be fantastic. And, when doing the compare, TX could also mark all changed objects as "dirty" again because they need deployment.
In addition, it would be great to be able to exclude items like execution package schedules and notifications from the transfer, because these often differ between dev and prod environments. In the current situation, they always get overwritten when doing a transfer.
Hi Wouter,
Not sure if it solves your question with execution packages in multiple environments. But it is possible to create a project perspective that contains the name of the environment.
You can add a condition on the execution package to execute only in a certain environment.
Hi Sigurður
Thanks for submitting your ideas. Your continued feedback on our product is very important to us. And so is your engagement in our community.
This is one of the most suggested features, and I have passed your input to our R&D department for further evaluation.
At the time of this posting, the current product roadmap is focused on a major evolution in foundational pieces of our software including splitting the development into ODX, MDW, Semantic Layer, and User Portal. With this evolution, we will continue to see incredible innovation in the product that may exceed your expectations or make the need for this feature obsolete.
Don't hesitate to let me know if you have any questions or would like to discuss further.
Thanks!
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
