No cleared state to return (For error recovery no message is returned.) Unable to link to transaction "fieldValue" because it has already been closed. The objectName object was saved successfully, but its corresponding Notes record could not be saved. The enum value "fieldValue" in the field "fieldName" is not supported by this implementation. The field "fieldName" is not supported by this implementation. Unable to represent objectName "fieldValue" in this version of the qbXML spec. Create the customer first, then you can send this request. If a customer named "Keith Palmer" does not already exist within QuickBooks, you'll get a 500 error indicating that the customer named "Keith Palmer" does not exist. So, for instance, you might have sent the following qbXML request: * This generally means that you've send a request to QuickBooks which refers to an object that doesn't exist. There was a required element("fieldValue") that could not be found in QuickBooks. The query request has not been fully completed. This is similar to error code 500, so see that error code for more details. Instead of just returning an empty list of objects, QuickBooks returns this error message. ![]() You'll get this error message if you issue a query of any type, but the result set is empty. The filters used in the query request did not return any matching objects from QuickBooks. The QuickBooks server processed the request successfully.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |