BICC Export/Import of Customization

Dave Kekish

We currently use the Export and Import Customization features to migrate PVO BICC changes between environments, and while this works well, it is less than I believe it should be.

For example, if you are altering a job in which you have multiple PVO's. and you removed a pvo from the job. Exporting the configuration and importing it to another environment where that Job was previously defined, will result in that PVO still being in that Job definition.

It is behaving as if all imports are additive only, what I would like is to see it be a replacement. I.e. Remove the existing job and create a new job based on the Customization file I am importing.

The same conditions exist for column removal, etc. It has gotten to the point where if I am altering a pvo in any manner, I export it from the source environment, log into the target environment and manually delete the job and its schedules prior to importing the same job/schedules.

I fully understand trying to be nondestructive in operations, but there should be a way to change that behavior on an import basis.