Copy a schema to another *and* move from environment 1 to environment 2
As in the title, I have a schema developed in an environment - let's call it "PROD" and I want to 1) do some major work on it, integrating in new tables and logic while leaving the existing in place for business use, so 2) make a working copy of it so I can work on it without impacting the business, and 3) do my work in DEV, because DEV is where DEV should take place ( don't @ me! ;-) )
Thus far I've
Created a placeholder schema _RAD_Testing in DEV and gotten the ID from it.
Exported the PROD version
Changed the ID from the PROD ID to the DEV ID of _RAD_Testing
Changed anything qualified with <orig>. to _RAD_Testing.
Changed the name and schema name in the loader file ( "?><loader name="_RAD_Testing" schema="_RAD_Testing" )
** Not sure what the xml:base= value should be - kind of guessing my _RAD_Testing schema ID_Loader and schemas/<new ID>_schema.xml ?
Saved the edited PROD files, ZIPPED, and attempted to import into DEV and .... didn't work. My _RAD_Testing looks just the way it did before and the original name schema threw all kinds of errors trying to commit which isn't surprising given all the changes I did.
Is there a documented process for this kind of task? And/or what (obvious?) thing am I overlooking?
Hi R. A. Dawson Sr I'm a little confused by your use case. If you are following our recommended best practice for Dev/Prod environments (Software Development Life Cycle), you would already have a copy of the PROD schema in DEV and that's the schema you should leverage for further development. Once complete and tested, you export from Dev and import that schema into PROD. If for some reason the schema does not exist in DEV, simply export from PROD and import into DEV directly. You really should avoid manual manipulation of XML. While there may be cases that require it, I'm not seeing a reason in this scenario. Apologies if I'm missing your point!