Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page is for administrators or expert users who need to move items from one PhixFlow instance to another

...

When the import is complete, the console reports log messages that list the imported items.

Very large imports may exceed limits on the server. If this happens, PhixFlow reports an Upload too large error.

Import and Updates to the PhixFlow Database

If Publish Streams is ticked, PhixFlow publishes data at the end of the import process, PhixFlow publishes imported data to the database. 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.

PhixFlow automatically rebuilds its database cache 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.

Note

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 due to missing items, the log console will include:

  • Error 612 messages - one message for each missing item. The message reports the item with the reference, and the item that is missing at the start, in the form
    item-type "name" (reference) refers to item-type (reference)

    Expand
    titleExample Error 612

    Area "inputform" (AreaComponent-08055461a13a51cb6914ca5be6dde21c) refers to Stream (Stream-36de2ecf9ecb2af08a42066d8c1fdd6a) but Stream (Stream-36de2ecf9ecb2af08a42066d8c1fdd6a) does not exist in the import zip or the repository.
    It is important for all referenced items to be imported. Please re-export from the source instance, including Stream (Stream-36de2ecf9ecb2af08a42066d8c1fdd6a)
    Note: To allow missing items when ALL AreaComponents refer to a Stream, consider adding AreaComponent.stream to System Configuration Allow Missing On Import. This will always null a reference from AreaComponents to a missing stream.


  • Error 618 message - one message summarising  this message includes the reference for all the missing items.

    Expand
    titleExample Error 618

    There are items missing from the import file. It is important for all referenced items to be imported.
    Please re-export from the source instance, including the following items:
    Stream-36de2ecf9ecb2af08a42066d8c1fdd6a

What to do

...


How to Find Missing Items

  1. In the console, find the Error 618 message.
  2. Copy the references for the missing items to a text file.
  3. Go back to the PhixFlow instance where the import file was generated.
  4. Go to
    Insert excerpt
    _administration
    _administration
    nopaneltrue
    Other Show in Repository,
  5. Paste one missing item reference into the field.
  6. PhixFlow opens the repository with the missing item highlighted.
  7. 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 this process to find all the missing items.   redo the export, making sure you include all the necessary items.Re-export all items you require; see Export Pane.

Ignoring References

In very rare circumstances, there may be a problem with references between types of item. If this occurs,  In this case, you can configure PhixFlow to "null" any relationship from one type of item to a missing instance of another type. For example, items from one instance can refer to users.  As different instances will have different users, the import will always fail PhixFlow to ignore (null) any references to missing users during an import.


Warning

Before deciding to ignore references, please discuss with PhixFlow support if there is

...

another way to resolve

...

your issue.

...

The support team can request that you allow imports to include incorrect references.

...

 

To configure PhixFlow to ignore specific references,

Go to  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 configurationOne 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.

...