Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Key

Bulk Import allows you to import the geographical definitions of your Assets from an existing system, rather than redrawing them all manually in Gruntify.

For example, you may have 100 garden bed assets in the system that require monthly maintenance. The garden beds already exist in a corporate asset management system, including their geographic location.

You can set up the Asset form for these garden bed assets in Gruntify, and then download the asset locations as a GeoJSON file (GDA84 coordination system https://datatracker.ietf.org/doc/html/rfc7946 ) or a CSV with Well-known text (WKT) representation of the geometry (See https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry). There is no download template like there is for Requests or Jobs.

Bulk Import is only available to users with an Owner role.

Process

Before starting the import, ensure you have:

  • Created a suitable Asset Form for your data. The names of the controls in the Asset Form do not need to match the names in CSV or GeoJSON file - you will be able to match up the names as part of the import.

  • An import file in CSV or GeoJSON file format, usually created by another computer system.

Steps:

  1. Select whether you want to use the GeoJSON format file or a CSV file.

  2. Choose which Asset type you want to use for the new Assets, by selecting the appropriate Asset form.

  3. Upload the GeoJSON / CSV file.

  4. Map the fields in the GeoJSON / CSV file to the Gruntify fields then click Next to start processing the file.

  5. Preview the results of the Import. If it looks okay, click Finish Import and click Confirm on the dialog to confirm updating the database. If there are issues, you can click Back to change the field mappings, or Save to create a Draft import and return to it later.

Once you click Finish Import and Confirm the import, Gruntify will start importing the Assets into the Gruntify database and you will receive an email with the results when it is done.

If you saved the Import as a draft, then you will be returned to the Asset Bulk Import menu. From here you can delete the draft if you want to start again, or reload the draft to continue processing.

Updating Assets

Requests and Job imports will create duplicate records if you reupload the same data. It is impossible to update the data already loaded.

Assets however can be updated. Get the Asset reference field, which is the AS-1AE66457 style id from the Asset screen, and include it in the import file.

This asset reference also appears in the Confirmation.csv file generated by the import and in the Asset Bulk Export .csv file. Either of these files may be useful to update the matching asset details in other systems, and then they can be included in your new import file when the assets change. Gruntify will match up the Asset IDs and will indicate that you are updating a record rather than adding a new record.

Mapping Fields

The key screen in the import is the Mapping screen.

The first column "Destination Control Header", is a list of the basic Asset fields such as Customer Asset ID, and the labels from the controls in the selected Asset form. The Asset form entries are at the bottom of the list.

The second column “Source File Column Header” is the field or column name in the import file. The “Source File Row Data” is the first three entries from the file, shown beside as a sample of the data.

The general mapping rules are:

  • The Asset Status values should be either "Active" or "Disabled". If you do not have a value in your import file for status, leave the entry blank and it will default to "Active".

  • Match each Control Header with a Column Header where the import file contains the appropriate data for that Control.

  • If there isn’t a matching entry in the import file and the header field is not mandatory, then that field will be left blank in a new asset, or not updated in an existing asset.

  • If there isn’t a matching entry in the import file but the header field is required (shown with an asterisk), then any default value given for this field in the form will be be used in a new asset. If updating, leave it unmapped and the field will not be updated.

  • If there isn’t a matching entry in the import file but the header field is required but no default value exists then an error will occur in creating a new asset. This may happen for a File field or a Media field as they do not have default values.

  • No labels