Specify 7.12.0
I have a bunch of changes to the stock schema, forms, and preferences which I’ve set up in my collection (like most Sp7 database owners) However, I want to set up another Sp7 database at our institution in mostly the same way. But it’s hard to remember off the top of my head how many changes I’ve made. I know I can copy form definitions and preferences in xml, but can I copy over the Schema / picklists somehow?
Alternatively, is there any way currently to summarize the changes between a default Specify schema/form set in a particular database / collection? Like for example with a query on certain tables?
It would be very convenient to be able to have a summary of the changes I’ve made to schema/forms so that I can make sure I make them in the new DB.
Hi @nfshoobs,
Great to hear from you!
You are absolutely right about the form definitions, preference files, and other app resources like field and table formatters; those are easily transferred by exporting and importing via App Resources.
Your Pick Lists and Pick List Items can be queried on, exported as a CSV file, and imported to the new database via the WorkBench. You can also use the “Find Usages” option in a pick list’s form meta menu to note where those pick lists are assigned in your current database.
The simplest way to extract other schema data is to export a JSON file of the schema localization. This is done with the “Export” button found in the table selection dialog for Schema Config.
The JSON file may need some prettifying or reformatting to improve usability, but it is pretty comprehensive!
Additionally, here is a query you can import as a jumping off point to extract your schema changes as a CSV file. It is based on the Discipline table and primarily includes fields from the SpLocaleContainer and LocaleContainerItem tables.
Schema.json (10.9 KB)
I don’t know why I’ve never noticed the “export” button next to the schema config menu! Thanks Bronwyn. 
Oh, wait, one more question. The query you linked, can I use it as a base query to make changes in the target DB’s schema via batch edit? Or will that break things?
