Exception Code | Description | Notes |
EventException001 | Error processing data | During the processing of a QDoc request, QXtend passed through the same field twice that was not the start of an iteration. The field in question can be found in the exception detail. |
EventException002 | Unexpected prompt field after delete | Unexpected field name in the events file for the delete confirmation prompt. The expected field name is usually the response to the QAD Enterprise Applications confirmation query: Are you sure you wish to delete this record? Review the events file or use QGen to update the file. |
EventException003 | Error while deleting | An QAD Enterprise Applications error occurred while deleting a record. Review the data in the QDoc and ensure that this data can be deleted. |
EventException004 | Unable to load an events document | The specified events file cannot be found or loaded. There may be invalid XML in the file. |
EventException005 | Error creating an event object | While adding a new events type, no Java class exists with the event name. Check the events file for the event types. This occurs only if the events file has been incorrectly updated. Review the events file for an invalid event type such as IterationEvent: <IterationEvent iterationname="supplier" exititeration="f4"/> |
EventException006 | Object is not an event | The event object created (see EventException005) does not conform to a specific Java interface. This occurs only if the events file has been incorrectly updated. Review the events file for an invalid event type such as IterationEvent. |
EventException007 | Incorrect iteration | Internal exception that arises when QXtend is attempting to resynchronize with the UI after an unexpected UI event. |
EventException008 | No name found for the iteration | Current field at the start of each iteration cannot be located in the events file. Review the events file for this program; it may need remapping using QGen. |
EventException009 | Invalid selection in selection list | The value entered in the QDoc for a selection list is not in QAD Enterprise Applications. Review the data in the QDoc and ensure that the selection item exists in QAD Enterprise Applications. |
EventException010 | No data in the QDoc | No data to process in the QDoc. |
EventException011 | Data sent too large | The data submitted for a primary field is too large. It may update an existing record rather than create a new record. Review the data in the QDoc. |
EventException012 | Ambiguous selection in selection list | Data for a selection list in the QDoc exists in more than one row in QAD Enterprise Applications. Review the data in the QDoc and QAD Enterprise Applications for this selection list. |
EventException013 | The QDoc has processed successfully but some QAD Enterprise Applications messages may have been lost | Occurs when switching from reading messages using the MessageReceiverServlet and the message area of the UI. |
EventException014 | Preprocess program name is null | The program name for the preprocess event is null. Verify the name in the events file. |
EventException015 | Error calling preprocess program | An error occurs while calling the preprocessor program. Review the events file. |
EventException016 | Preprocess – Updated iteration node does not match existing iteration node | The preprocess program changes the name of the current iteration. This is invalid. Correct the preprocess program code. |
EventException017 | Postprocess – Updated response iteration node does not match existing response iteration node | The postprocess program changes the name of the current iteration. This is invalid. Correct the postprocess program code. |
EventException018 | An attempt was made to access invalid events data. See context for details. | The events data file does not match the fields in the QDoc. |
EventException019 | An error was encountered when updating a node using the QXI preprocessor or postprocessor. |