Error Messages Triggered for Data Adapters
Detailed view provides the following information about any error messages triggered for Data Adapters:
| Field | Description |
|---|---|
| Error returned for Data Adapter | Name of the Data Adapter for which the error was returned. |
| Error message: | Relevant error message. For example, Invalid configuration. |
| Occurred on: | Date and time that the error occurred. |
| Status code: (if applicable) | Standard HTTP error code. |
| Content Length: (if applicable) | Size of the response body (in bytes). |
| Content Type: (if applicable) | MIME type of the response body. |
| Error Response: (if applicable) | A detailed message returned from an external service for an HTTP Error (HTTP Body), except when it's an HTML MIME type. Alternatively, a detailed message about the root cause that triggered the error. for example, the JSON Parse error example, shown below.. |
Examples
404 Not Found Error
Highlights an issue with the client-side data provided to MXO
. The requested data does not exist or has not been made available to MXO
.
500 Internal Server Error
For security reasons, MXO does not provide extra information about configuration issues relating to HTML pages being returned.
JSON Parse Error
Highlights an issue with the format of the data being sent to MXO (including the location of that issue in the response body). In this case, there’s an unexpected character in the data.
JSON Missing Field or Attribute Error
Highlights a missing field or attribute in the data being provided to MXO . In this case, the data being sent is missing the AddressLine1 defined in the Accounts Data Adapter schema.
