1. SuiteCloud Platform
  2. Core Plug-ins
  3. Financial Institution Connectivity Plug-in
  4. Financial Institution Connectivity Plug-in Interface Overview
  5. Administering a Financial Institution Connectivity Plug-in
  6. Error Handling for Financial Institution Connectivity Plug-ins

Error Handling for Financial Institution Connectivity Plug-ins

This section explains how to surface user-facing errors from your connectivity plug-in in NetSuite, using both the legacy (free-text) and new (standardized error code) methods. Transitioning to the standardized method ensures that your plug-in provides actionable and consistent feedback in NetSuite.

Free-text failure reasons will be phased out in favor of standardized error codes. Until this happens (which will be in a future release), both legacy and standardized methods are supported, but you're strongly encouraged to update your plug-in as soon as possible.

Legacy vs. Standardized Error Handling

There are two approaches to handling user-facing errors, depending on your plug-in implementation. The legacy method surfaces user-facing errors by raising exceptions with free-text message values. The standardized method surfaces user-facing errors by raising exceptions with standardized errorCode values and required properties. Each approach applies to import-level and account-level errors. Refer to the following procedures for code samples and step-by-step guidance for each error type.

For information about updating your parser plug-in interface for import-level and parser error codes, see the help topics Updating Parser Plug-ins for Import Error Codes and Updating Parser Plug-ins for Parser Error Codes.

Note:

All custom or third-party plug-ins should be updated to use standardized error codes as soon as possible.

For the full list of available error codes and scenarios, see Bank Import Error Codes (Reference).

Related Topics

General Notices