Errors Encountered When a Submit Button Is Clicked In an Intelligent Advisor Interview

If an error occurs at the end of an Intelligent Advisor interview, or after you click a Submit button part of the way through the interview, it is likely the web service connector has encountered a problem processing the Save request or Save response.

When the Submit button is clicked, the current screen will display one of the following error messages. These errors are logged in the Message log.

"An error occurred trying to process your request" errors

The following table contains the message log codes, the message which appears for each error and the likely cause.

Note: Every message covered in the table below begins with the header text Error for policy model [Deployment Name]:[Deployment Version] - . For ease of lookup, only the portion of the message which follows the header has been reproduced in the table.

Table 1. Description of web service connector errors encountered on submit with the message 'An error occurred trying to process your request. For further assistance please contact support'
Message Log Code	Message	Likely cause
OPA-DATA-109	via connection: [Connection Name] Failed to load data from data service Fault code: [Fault code] Fault String:[Title of fault] Message: [More details]	The connector responded with a Request Fault, and this message displays the information it contained. This error is likely to occur after a long pause. For more information, see Handle errors when loading or saving applications data.
OPA-DATA-108	Read timed out	The connector took too long to respond to the Save request. This error is likely to occur after a long pause.
OPA-DATA-108	Field with name '[Field Name]' already exists in row '[Row ID] of table '[]'.	Two output `Fields` in the same response `Row` have the same name. You may have accidentally duplicated one, or used an incorrect name on a second `Field`.
OPA-DATA-108	No mapping for exists field '[Field Name]' in row '[Row ID]' of table '[Table Name]'.	A `Field` was included in a `Row` which was not requested as an output `Field` in the Save request. Do not include `Fields` unless they are explicitly requested. Alternatively the ID may be incorrect.
OPA-DATA-108	Error parsing data: expected the start of an attribute value element	A requested `Field` was missing an element describing its value. A `Field` must have one of the possible field value types.
OPA-DATA-108	Error parsing data: Unexpected element. Expected: change-point. Actual: [Received element type, e.g. ‘text-val’]	A second value was included in a `Field` which does not correspond to an attribute with temporal values in the policy model. `Fields` can only have one value element unless they are temporal, in which case they must also have at least one change-point element. For more information, see Support Temporal Values.
OPA-DATA-108	Row '[Row ID]' already exists in table '[Table Name]'.	Two `Rows` for a `Table` have been given the same `id` attribute value.
OPA-DATA-108	Entity instance already exists in the model: [Attribute Name][[Row ID]]	A `Row` was included with an `orig-id` equal to the value of the `id`attribute of a previous row from the same table. The `id` of a `Row` can only be changed once per transaction. Caused by something like: <row orig-id="entity1" id="new ID"/> <row orig-id="new ID" id="second new ID"/>
OPA-DATA-108	null	The `Root Table` (the `Table` mapped to the Global entity in the policy model) was returned without a `Row`. The `Root Table` must always have a single `Row`. Your policy model likely has a load after submit mapping and the load after submit data is not being returned correctly. Turning on debug logging may give you more insight into what is going wrong.

"This value is of the wrong type" errors

The following table contains the message log codes, the message which appears for each error and the likely cause.

Table 2. Description of web service connector errors encountered on submit with the message 'This value is of the wrong type'
Message Log Code	Message	Likely cause
OPA-DATA-108	Error for policy model [Deployment Name]:[Deployment Version] - Error parsing data: Unexpected element. Expected: change-point. Actual: [Field Value Type]	An output `Field` had a value returned to it with the wrong field value type. For example, the `Field` was described in the Metadata as a STRING, but a value within a `number-val` was returned.
OPA-VAL-003	Error setting value for attribute '[Attribute Generated ID]' in policy model [Deployment Name]:[Deployment Version] - Temporal value contains bad change point dates after [Date] java.lang.IllegalArgumentException: Temporal value contains bad change point dates after [Date] at [More stack trace]	A `Field` mapped to a policy model attribute with temporal values was given two or more `change-point` values which were not in chronological order by their date attribute values. Include `change-point` elements from earliest to latest dates. For information on how to implement `change-points`, see Support Temporal Values.