Data file error handling
When you bulk load account data into IBM® Envizi ESG Suite, the errors that can occur can be grouped into application errors, parse errors, and load errors.
Summary of error categories in Envizi ESG Suite
When you bulk load account data into Envizi ESG Suite, the following
categories of errors can occur:
- Application errors
-
Related to receiving, unpacking, and interpreting the received data. The errors occur at the application layer, and they can be captured and presented if data is provided to Envizi ESG Suite through a client-specific data service such as S3, sFTP, or a client-specific email address instead of through the former generic file loader email addresses.
- Parse errors
- Occur during the parsing of data. The errors are related to the structure and format of the data that is being processed.
- Load errors
- Occur during the loading of data into the system. The errors are related to the integration and storage of the data within the system.
Previously in Envizi ESG Suite, visibility of parse and load errors was provided through the Files Processed - Accounts & Setup page. With the introduction of data flow automation, application layer errors are now captured and presented more effectively. By using data flow automation, you can enhance your data security and auditability, while having increased visibility of error messages as files are processed.
Error messages table
The following table lists error messages with their associated error category, as indicated
previously, and associated file failure status. If the file failure status is
Yes,
all records are prevented from loading into Envizi ESG Suite. If the file
failure status is No, an error might be displayed but the records are partially
loaded into Envizi ESG Suite. The table also shows associated connector types
because some errors are specific to the upload process or connector that ingests the data. Account
data can be ingested through one of the following connectors:- Standard
- The generic account loader that was configured for early Envizi ESG Suite users for any custom connectors.
- Universal
- Correlates to the single Account style account setup and data load report template.
- PM&C
- Correlates to the multiple account style single file, primary measure, and cost report Account setup and data load - PM&C template.
- Multi-ACS
- The flat file format report template that supports multiple account styles and multiple measures.
- All
- Indicates applicable to all loading types.
| Message | Error category (application, parse, or load) | Connector Type (standard, PM&C, universal, multi-ACS, or all) | File failure status |
|---|---|---|---|
| IntialiseUploadConnection(): File Processing Start | Parse | All | No |
| CloseUploadConnection(): File Processing End | Parse | All | No |
| The line is skipped as the column values are empty | Parse | All | No |
| The line is skipped as the row number is present in the skip row list | Parse | All | No |
| The line is skipped as it is empty | Parse | All | No |
| The line is skipped as it is matched by a SKIP row name | Parse | All | No |
| Start row number {0}. End row number {1}. The total number of lines | Parse | All | No |
| Error opening file | Application | All | Yes |
| File Specification Not Found | Application | All | Yes |
| File contains no valid data rows | Application | All | Yes |
| Unable to match the file recognition row | Application | All | Yes |
| More than one file specification has matched the file | Application | All | Yes |
| Error while connecting to database | Application | All | Yes |
| Error Finding the Account Style | Application | Standard, PM&C | Yes |
| Error when converting value [Col_Value] to INTEGER. Input string was not in a correct format | Parse | All | No |
| Supplied row number[X] and pattern[Y] is invalid | Application | All | No |
| File specification entry [File Spec Name] is not correct. The pattern is empty for row type file recognition | Application | All | No |
| Unable to find a suitable replacement pattern | Application | All | No |
| Unknown account target column {Colum_Name} | Application | All | No |
| Tab [Tab Name] is not found in the excel file | Application | All | No |
| DATA_READ_WRITE rows found but FILE_RECOGNITION row is not yet found | Application | All | No |
| Index out of bounds. Trying to access column number {N+1} while the line has only {N} columns | Application | All | No |
| The column values does not lie within the range | Application | All | No |
| Invalid AWS credential configuration | Application | All | No |
| Credentials from Secret Manager is not available, secret name | Application | All | No |
| The file you are accessing {File Name} are currently in use | Application | All | No |
| Error copying file to target directory | Application | All | No |
| EXCEL could not be started. Check that your office installation and project references are correct | Application | All | No |
| Failed to sort file data | Application | All | No |
| Unknown Exception | Application | All | No |
| Illegal characters found in money field | Load | Standard, PM&C | Yes |
| Illegal characters found in date field | Load | Standard, PM&C | Yes |
| Column value cannot be null or empty | Load | Standard, PM&C | Yes |
| One or more Airport codes could not be found | Load | Standard, PM&C | Yes |
| Account Style is invalid | Load | All | Yes |
| Account Style Id is invalid | Load | All | Yes |
| Start or end date falls outside normal operational range | Load | All | No |
| The date period covered by the record for account should overlap with the period between account's Opened On and Replaced On dates | Load | All | No |
| Warning: Start Period > End Period. Record is ignored from the file | Load | All | No |
| The Start Period and End Period of the record for account should be between the account's Opened On and Closed On dates | Load | All | No |
| Cannot support multiple Account Styles | Load | Universal | Yes |
| Account style label is not valid | Load | Universal, Multi-ACS | Yes |
| Picklist value is not valid | Load | Universal, Multi-ACS | No |
| Cannot support multiple organizations | Load | Universal, Multi-ACS | Yes |
| Combination of organization name and link is not valid: | Load | All | Yes |
| Account style does not support selectable subtypes | Load | PM&C, Universal, Multi-ACS | Yes |
| Account style is locked to a subtype so record level subtypes are not supported | Load | PM&C, Universal, Multi-ACS | Yes |
| Account style uses selectable subtypes so account subtype should be set to selectable or a specific subtype | Load | PM&C, Universal, Multi-ACS | Yes |
| Account style is locked to a different subtype than the one being passed for the account. Either leave it blank or set it to the correct subtype | Load | PM&C, Universal, Multi-ACS | Yes |
| Account is locked to a specific subtype so record level subtypes are not supported | Load | PM&C, Universal, Multi-ACS | Yes |
| Account is being set to selectable so record must be set to a specific subtype | Load | PM&C, Universal, Multi-ACS | Yes |
| Existing account does not have the same account subtype as the value in this file | Load | PM&C, Universal, Multi-ACS | Yes |
| Account subtype not supported by account style | Load | PM&C, Universal, Multi-ACS | Yes |
| Record subtype not supported by account style | Load | PM&C, Universal, Multi-ACS | Yes |
| Record subtype must be set for a selectable account | Load | PM&C, Universal, Multi-ACS | Yes |
| Unable to resolve associate | Parse | All | No |
| Unable to resolve location | Parse | All | No |
| Unable to resolve account | Parse | All | No |
| Row failed due to unknown value in "Update" column | Parse | All | No |
| Required column is not set: [Column_Name] | Load | All | Yes |
| Database error like length/conversion | Load | All | No, however, if error occurs while processing the rule then data will still be loaded |
| File cannot be loaded because some of the records would overwrite locked data | Load | Standard | Yes |
| Account item <b><font color="#E41B17">[parm1]</font></b> would overwrite locked data | Load | Standard | Yes |