Import not overwriting routines
Posted: Thu Sep 02, 2004 5:22 am
As a result of another issue, we have found that when we import a .dsx into our production project (let's call it Proj C), new versions of routines do not overwrite the existing versions. The process we use to go from development to production is (we understand that this is not 'best practice' and are currently reviewing the process):
We develop in Proj A.
When we are happy with our work (
), we promote these modules to Proj B for usertesting using Version Control - these are promoted as read only objects.
Once these modules have been successfully tested, we do an export from Proj B of executables only.
We finally do an import of these executables into Proj C.
We have noticed that this process does not replace the existing routines with the new version - to my knowledge we have not experienced a problem with the replacement of jobs/sequences; only routines. We are currently doing some more investigation, but I am not certain if this happens all the time or whether it is a 'now and then' thing - we have some routines that have supposedly been modified and promoted a number of times over the last few months, but still have the initial import date attached to them.
When we imported the specific .dsx that highlighted this problem last week, we were prompted as to whether we wanted to overwrite modules - to which we replied 'yes' on every occasion. We were only prompted a couple of times, not for all the modules in the .dsx that existed in the project.
Is there any reason why a new routine would not over-write an existing routine? (apart from when you are prompted with that very question and you say no)
To allow us to continue processing, we have created a new production project and imported all modules from Proj B - this has worked fine and everything seems to be working correctly. But obviously we need to; 1 - find out the reason behind the problem, and 2 - Build a better way of promoting modules between projects (Version Control was not considered an acceptable overall method by the organisation).
As per usual, any help is greatly appreciated.
We develop in Proj A.
When we are happy with our work (
![Shocked :shock:](./images/smilies/icon_eek.gif)
Once these modules have been successfully tested, we do an export from Proj B of executables only.
We finally do an import of these executables into Proj C.
We have noticed that this process does not replace the existing routines with the new version - to my knowledge we have not experienced a problem with the replacement of jobs/sequences; only routines. We are currently doing some more investigation, but I am not certain if this happens all the time or whether it is a 'now and then' thing - we have some routines that have supposedly been modified and promoted a number of times over the last few months, but still have the initial import date attached to them.
When we imported the specific .dsx that highlighted this problem last week, we were prompted as to whether we wanted to overwrite modules - to which we replied 'yes' on every occasion. We were only prompted a couple of times, not for all the modules in the .dsx that existed in the project.
Is there any reason why a new routine would not over-write an existing routine? (apart from when you are prompted with that very question and you say no)
To allow us to continue processing, we have created a new production project and imported all modules from Proj B - this has worked fine and everything seems to be working correctly. But obviously we need to; 1 - find out the reason behind the problem, and 2 - Build a better way of promoting modules between projects (Version Control was not considered an acceptable overall method by the organisation).
As per usual, any help is greatly appreciated.