Adam:

Would you be more specific with your question?  What message you want to turn off?  QXtend Inbound or QXtend Outbound?  Response message?  Exception Message?

Cheers

Gary

Hello Gary,

Thanks for your response. The operations displaying messages are inbound. There is a custom application that sends data to QAD in order to create records in several tables (pt_mstr, ptp_det, ro_det, etc). The messages received are valid and are telling us that some data is not correct. However, as we are creating  hundreds of records in one go, we’d prefer all this info to go to a file that could be read by the user after all transactions have been processed. In this way, we could leave the program to run unattended (at the moment the user has to stay next to the computer while the program is executing clicking the OK button). We are invoking several QXtend Apis, and I thought maybe there is a way to disable messages in general (like we do with triggers).

Thanks for any ideas or suggestions,

Adam

Adam:

In that case I think you should really look into how you design the program which posts messages to QXtend Inbound via SOPA call - the exception messages SHOULD ALWAYS be send in the SOAP responses and it is up to the calling program to determine what to do with it.  

Gary

Another way we handle this is to load the data into our own custom  tables using qxtend inbound.
Then we have custom programs that process the data that do their own error checking and cim loading when necessary.  This takes the burden off qxi for mass data loads.

@Daniel, this is an interesting solution design. Once data is uploaded in the QAD db, users have less "barriers" of correcting/reading data. Of course, depending on the situation it may or may not be allowed to use this design model.