Skip to main content
SUBMITTED

Selective environment transfer (partial release)

Related products:TimeXtender Data Integration
  • May 31, 2023
  • 1 reply
  • 69 views

Forum|alt.badge.img

I am encountering an issue with the environment transfer process, specifically the requirement to transfer the entire DEV project without the ability to select specific objects for transfer. This limitation results in incomplete objects being transferred to PROD that lead to execution errors. Moreover, the current transfer process prevents us from making further developments on objects (in DEV) that are already included in execution packages on PROD. TimeXtender enables team development, but in a large project where 3-4 individuals work simultaneously, it is crucial to have the ability to transfer one's own work without including their coworkers' work in the transfer.

Let’s take an example. Table A is part of a semantic layer that is refreshed on a hourly basis. I am developing table A further on DEV but it is not ready for Production yet. Suddenly a request arises from an inhouse department that they want table B on PROD as soon as possible. I add table B to the DEV environment and transfer it to PROD. But with the transfer all the changes from table A are transfer as well. I don´t want to show the changes on PROD but if I do not deploy the table I will get execution errors and the semantic layer will not refresh.

An ideal solution for this problem would be to include a selective transfer option, allowing me to choose which objects are transferred to PROD.

1 reply

  • Contributor
  • March 10, 2025

Really important feature. The bigger the team gets, the more likely it is to block each others deployments. Selective deployment/promotion would be really helpful here, like creating and merging a branch in git.