Thefunctionality gives the user the ability to bulk import events.
The format of the Excel workbook needs to be very specific. It is recommended you use the Example button on the first page of the Import wizard to generate the workbook in the correct format for importing data.
Finding trigger checks are run on each event during the import process, or whenever an event is edited, or the Anomaly Triggers Tool is run from the Event Listing. Please note that the Anomaly Trigger tool is only run on the filtered list of events in the grid and should only be run if Anomaly Trigger limits have changed. During the check:
If it fails (meaning data is outside of defined triggers), then it will create a new finding. We first match on the following to see if the finding already exists. It matches on:
- Anomaly Trigger rule (Bound_ID)
- Is Auto Generated = true
In other words, if there is no finding already created from this trigger for this event, NEXUS will create a finding.
If you do not specify a Survey Set for event survey data to be imported into, it will be imported into Raw Survey Data, which is the default set. If two different events have the same date/time, the second one imported will overwrite the survey values of the first. To avoid this, don’t have two different events in the same survey set at the same time with different survey data.
When creating a new event, Event.Start Clock must be earlier in time than Event.End Clock for the import to succeed.
The Import Wizard¶
If the importer encounters a completely blank row in an Excel file, it will stop importing at that point, even if there are non-blank rows further down. This can provide an easy way to test an import sheet: set it up, and then after just one or two rows of data, insert a blank. Run the import to see if it’s doing what you expect, and if so, delete the blank and run again. Similarly, if the importer encounters a blank column in an Excel file, columns to the right of this will not be imported.
You can have one ‘Asset Location.Full Location’ column, with levels in the asset hierarchy separated by space slash space, like ‘My Field / My Platform / My Member’, or many ‘Asset Location.Full Location’ columns, with one asset hierarchy level in each. (But you can’t mix the two, with one containing ‘My Field / My Platform’ and a second containing ‘My Member’.)
Sometimes a single “master” row will have several “detail” rows. For example, an asset information row might have several sub-AIG rows; or an event might have several findings or several multimedia images or both. When this occurs, you should repeat the row, with different “detail” values in each.
For example, if you have several multimedia images to import against a single event, your Excel sheet should have several rows that are identical except for the Multimedia.Name and Multimedia.Image columns. If you have specified an event number, and you use the same event number on each row, NEXUS will only create the event once, but will create several multimedia items. (If you do not specify an event number, NEXUS will instead create several different events with one multimedia item each.)
It is also acceptable to leave event fields blank for all except the last row — under the hood, NEXUS is importing each Excel row into the event, and only the last Excel row imported will “stick”. Note that if your event has a finding, you should not repeat the finding data on each event row — if you do, NEXUS will create one finding for each Excel row that has finding data filled in.
In some cases you do want multiple findings on one event, and in that case you should fill in several rows as appropriate. Similarly for sub-event data or sub-AIG data: if you want several different sub-events or sub-AIG rows imported, you should repeat the event row or AIG row with different sub-event or sub-AIG data in each case. If you are repeating an Excel row for another reason and you do not want several sub-event or sub-AIG rows imported, you should fill in sub-event or sub-AIG data in only one of the Excel rows.
During an import, we communicate with Excel “behind the scenes”: we command Excel to open the file you want to import, and ask Excel what’s in each cell. An upshot of this is that if you use Excel to modify the file while we’re importing it, even if you don’t hit Save, you may confuse the import process. Similarly if you take a variety of other actions: using Save As, closing Excel, etc. If you see error text “Call was rejected by callee”, this is what’s happened: Excel has stopped answering our calls.
It is possible to create new Asset Hierarchies by importing Assets with hierarchy structures that don’t already exist. In doing so, new Parent Assets will be created. In case this is not the desired result, the Test Import will throw a warning, for example:
Line x: Parent Asset “Example Parent” will be created for the location “Wood / Example Parent / 00C-2401A”
“xx new Parent Asset(s) will be added.”