I have a test environment where I can develop and a production environment where I don't have access due to regulatory conditions. In order to bring changes into production, I have to create appropriate packages, which are then imported there.
I did some minor changes in the DFD and exported the Batch Type. However, it was not possible to update the existing batch type using the import function. Error message : Batch Type already exists
I then tested the following in the test environment:
Delete the Batch Type with all corresponding Document Types and DFDs and reimport the Batch Type.
Result: I can't import the batch type again because it supposedly still exists. Same error message as before the deletion. I'm assuming there are still some links in the database that are causing this. This really got me into trouble as my backup was the batch type which I couldn't import anymore. I then started disassembling the Exported file to at least extract the DFD data and reconstruct an import file for the DFD, otherwise I would have had to build the DFD from scratch.
When I export/import a DFD I create a copy. Here I have to delete the old DFD, rename the new one and adjust the links. The training data in the test environment for this Batch Type is completely lost. I think its still linked to the old Document Type/Batch Type, which I cannot import anymore. Luckily it wasn't the big loss in this case.
Before I step from one trap to the next, here are my questions:
What is the best way to bring changes from the test environment to production?
How can I create/use proper backups?
- Batch Type
- Document Type
- Training Data