If in doubt about the appropriate import/export method for any given file, assume the following to identify the appropriate method:

To identify files in the standard distribution (Config subfolders)

•All the files under config/global are configurations, to import with cmd4 config in and to export with cmd4 config -out.

•All the files under config/data are objects (data), to import with cmd4 import and to export with cmd4 export.

•All the files under config/strings are strings, to import with cmd4 strings -in and to export with cmd4 string -out.

•All the files under config/icons are icons, to import with cmd4 icon -in and to export with cmd4 icon -out.

•All the files under config/schemas are schemas, to import with srv4 dbschema o dbupdate.

Of course, this method is not 100% safe, as someone may put an arbitrary file in any of listed folders and forget about it.

To identify an arbitrary file

To know what is indeed a file XYZ.xml, open the file and look at the root element.

•If the root element is <GN4ShellConfiguration>, or <opt:XmlExportOptions, it is a configuration, to import with cmd4 config in and to export with cmd4 config -out.

•If the root element is <objects>, these are objects, therefore to import with cmd4 import and to export with cmd4 export.

•If the root element is <xs:schema, it is a schema, to import with srv4 dbschema o dbupdate.

•If the root element is StringList it is a definition of translation strings, to import with cmd4 strings -in and to export with cmd4 string -out.

•If the root element is KeywordList, it is a definition of keywords, to import with cmd4 keywords -in and to export with cmd4 keywords -out.

•If the root element is InstallConfig, it is a setup configuration, to import with srv4 dbupdate -config.

•If the root element is something else, it could be puo’ essere config, object o una cosa che non c’entra un fico con gn4.

If you suspect it may be an object, review the schema in the browser as explained in Review the schema in a browser, and then search for the name - if it is in the schema tree, it is an object, therefore to import with cmd4 import and to export with cmd4 export.

If the item is not in the schema tree, look at the namespace. If there is no namespace, it may be an object valid for the 3rd party system from where it was generated, but not for GN4, because the schema is different.

If the namespace is xmlns="urn:schemas-teradp-com:gn4tera", it is an object, therefore to import with cmd4 import and to export with cmd4 export.

If the namespace starts with http://www.teradp.com/schemas/GN4/1/, it is a configuration.