Transfer Timextender to another Server

Hi Christian!

I have followed that manual, but I'm running into somethings, mainly the mapping. It seems that everytime I push the DEV MDW to the PRD MDW I have to remap all the tables. This cannot be right? I try to follow that manual as close as possible, but some things are a bit vague. The ODX is transfered without troubles. Next I synchronize and transfer the tables. No problem.

After that I copy the DEV MDW instance to the PRD MDW instance. Then I login to the PRD server and do synchronize with ODX. The synchronize mapping is greyed out under advanced. Next I have to remap all the tables. In many cases some fields fail and I have to remap these manually. (A small quality of life improvement: searching in the list of fields by pressing the first letter also jumps to that field and adds it. For example. I need to map No_ and press N. It jumps to Name and immediately maps that, removing it from Name, so I have to go back again and change that. In large tables quite tedious).

After having worked through all the remaps I can deploy and execute. However, If I now make a change in the DEV MDW and copy that instance again, I have to remap everything again. What is going wrong?

BR,
Maarten

Hi @Bitmetric_Maarten yes the current process requires remapping each time the instance is copied. The fully-fledged multi-environment functionality that we are working on will greatly simplify the promote process.

Thank you for your quick reply. Unfortunately to hear, but alas, it is how it is. Could you give an indication when the new environment will be released aprox?

@Bitmetric_Maarten I am unable to provide a timeline at this time, but it will most likely be released in the next major release