When importing a Data Exchange file, BEACON scans the file line-by-line/row-by-row, examining subsets of parameters within each line. The validation process also scans for file-level errors such as missing or unrecognized column names and non-Data Exchange content. When the scan is complete, an Exceptions Report is generated.
To download the report, click Download Exceptions. To view the report, click View Exceptions
or click the Exceptions link in the Assets>System Sync>Activity List.
Errors
Validation errors are mistakes that must be corrected before proceeding with the import.
There are two kinds of errors that can happen during import:
1. File-level errors
-
-
-
These affect the entire file.
-
Example: The file type isn’t supported. This can happen when you attempt to import a photograph, an Excel-format file, etc.
-
Result: The whole file is skipped and not imported.
-
-
2. Field-Level errors
Field-specific errors affect only the part of the service they relate to.
A service is built from several components—Accounts, Locations, Meters, and Endpoints and their related data. When an error occurs in one of these components:
-
-
-
The error blocks updates only to that specific component or related fields.
-
Other components in the same service–for example, if the error is with a Meter-related field–Account, Location, and Endpoint-related data will still update successfully.
-
This ensures that valid data continues to be imported, even if part of the service has issues.
-
-
In other words, errors don’t invalidate the entire record—they only prevent updates to the portion of data that’s incorrect, while the rest of the service is updated as expected.
Warnings
Pay close attention to validation warnings. They inform you when data in a Data Exchange file is going to make a service configuration change. For example, changing the location of a meter or endpoint, closing one service agreement and opening another, etc. Retroactive changes can have significant consequences, for example, changing existing histories at a given location. If the change is one that you intended to make, then it is safe to proceed with the import. If, however, you did not want to make the change, then you should cancel the import, locate the particular record and change the offending data.
