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, if items refer to other items in a package, ensure the package is 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.
If an import fails, check the console for log details. If there are missing items, the log will include
Error 612 - one for each missing item in the form: item-type "name" (reference) refers to item-type (reference)
Error 618 - one message summarising all the missing items.
What to do
- Copy the list of missing items from Error 618 to a text file.
- Go back to the PhixFlow instance where the import file was generated.
- Go to
Administration → Other → Show in Repository, - Paste one missing item reference into the field.
- PhixFlow opens the repository with the missing item highlighted.
- Do something that means the item will be included in the export, Can the export window be open at the same time? Add it to a package, something else?
.Repeat for all the missing items. redo the export, making sure you include all the necessary items.
In very rare circumstances, there may be a problem with references between types of item. If this occurs, discuss with PhixFlow support if there is a way to resolve this issue. If
The support team can request that you allow imports to include incorrect references.
Only in this situation, you can use System Configuration → Allow Missing on Import option to allow PhixFlow to "null" any relationship from one type of item to a missing instance of another type.
What to do
In the console, find Error 612.
copy the <from object>.<to object> string
Go to System Configuration and find Allow Missing on Import
Paste the string into the field
Save the configuration
One example where this option is useful is when items from one instance refer to users. As there users should not have access to the import instance, <from item>.users allows PhixFlow to ignore (null) these references.
All log messages have a ? that goes to the system console help YOu need a link to troubleshooting import to here.