Selecting Import Configuration from the Administration Menu will take you straight into a file browser. Select the configuration file you wish to import, and continue. You will be taken to the Import Configuration form. At this point you can press Choose Files to change the configuration file you will import, or Upload to continue with the import.
After selecting the configuration file, a form will appear to enter a password to import encrypted fields. This is the password which was set during export. If no password is entered then no encrypted data will be imported.
If Publish Streams is ticked, publishing will be run at the end of the import. This means that changes to streams and stream attributes will be applied to the stream data tables in the database. If publishing fails, the import will still complete successfully, and the publishing errors will appear in the console. See also Publishing Streams.
When import is complete log messages in System Console will list which objects have been imported.
If translation is configured, audit trail changes to drop-down field now have the translated name of the option.
PhixFlow will automatically start to rebuild its database DTO caches when the import completes. We recommend that you run large import processes during periods of low system usage, for example overnight. This gives PhixFlow time to complete the import and rebuild the caches without affecting the performance seen by users.
Very large imports may exceed limits on the server. If this happens, PhixFlow reports an "upload too large" error.
Managing Missing Items
When you export items from one PhixFlow instance, it is important to ensure all items are present. For example, ensure any packages required by items are included in the export. The import will fail if there is a reference to an item that does not exist:
- either in the import file
- or in the target system.
Ask Eleanor to show me this as there is additional functionality and a new item
Other Actions → New option. Paste the string from console to find the thing with a problem. The message is on the target system, but you need to put the string into the source system
Check taht the message to go into the finder - is it finding the object that is missing (it should be!) or the object that's expecting the missing thing
PhixFlow reports the missing items in the console messages. You may need to redo the export, making sure you include all the necessary items.
You may need the import to complete, even with an item missing. In this case, use the System Configuration → Allow Missing on Import option to specify the file name of the missing items, then rerun the import.