PROCEDURE FOR ASSET XML IMPORTS

The first step to perform prior to making any XML import is to generate an XML export of the data
you want to update in ASSET as illustrated below;

The INDEX001 file contains references to all XML files generated. Once this is opened, it opens all
other associated XML files. Alternatively individual XML files can be opened by selecting them using
CTRL + Mouse Click

The generated XML files can easily be viewed by opening XML Data Editor as illustrated below;

The contents of the XML files can easily be copied and pasted into Excel for easy editing. Care must
be taken when performing the following actions;
1. Deleting the contents (rows) of any parent network entity results in all lower level contents
of child entity (rows) being deleted. Direct paste without deleting can be useful to avoid this
problem.
2. Strict adherence to the data types of the columns must be kept, otherwise errors will result.
It is useful to constantly monitor the message log in case of any errors arising.
3. Some formatting may be lost when copying and pasting to Excel. This can be easily corrected
from analysis.

Once XML data has been modified as desired, next step is to save the files for import into ASSET. This
is easily achievable as illustrated below;

Once XML files have been modified or appended as desired, next step is to perform ASSET import
procedure as illustrated below;

Select how you want conflicts/differences to be handled during import process. The
following options are possible;
1.
2.
3.
4.

Prompt on an individual basis

Replace the data in the project for all conflicts/differences
Merge the data
Leave the existing data as it is.

Once appropriate option is checked, click Import to begin importing. During import:

If you do not have permission to create or update an object type that you are trying to
import, you are given the choice of stopping importing or ignoring.
If the user specified in your import does not exist in your database, the user will default to
the current user.
If an imported element's parent does not exist in your database, a dummy parent is created
prior to its import.
If there were any problems, messages are shown in the message log.
When you replace, the existing information is overwritten with that in the XML import
file. This applies even if there are blanks in the file; for example, neighbours of a cell are
deleted and replaced with the imported blank list, so the cell would then have no
neighbours.

Important: It is recommended that you manually check the XML file created in the XML
Data Editor before you import it into ASSET.
Unless you are editing an existing file, it is recommended that you select the Merge option in
the XML Import dialog box, particularly when dealing with sparse XML data:
Warning: If you choose Replace, the target item will be completely overwritten with the
content of the XML file. Ensure that you have a backup of your original data before using the
Replace.

Replace can be very handy for purposes of deleting data but care has to be taken that
XML import file has all current data in Database with exception of whatever is
desired to be deleted.