Right now, a lot of failures seem to slip by without any action take and then are never processed again. We need to come up with a better solution to either set the status on the failed exports to retry next time web connect is run or mark then as failed and log the reason so the customer can remedy. Here are a list of failures I have received while testing this module:

  1. 3090 - Errors: There was an error when storing "PRODUCT:NAME" in the "item inventory name" field. QuickBooks error message: Names in this list cannot contain a colon. The colon is a special character used to indicate a parent/child relationship.
  2. 3100 - The name "Conserve Water Educators Guide" of the list element is already in use.
  3. 3180 - There was an error when saving a Item Inventory list, element "TEST PRODUCT". QuickBooks error message: An income account must be specified.
  4. 3000 - The given object ID "933498f4-1bd7-4db1-92f6-47cd5cf67745" in the field "list id" is invalid.
  5. 3140 - There is an invalid reference to QuickBooks PaymentMethod "Manual" in the SalesReceipt. QuickBooks error message: Invalid argument. The specified record does not exist in the list.
CommentFileSizeAuthor
#5 2943362.patch1.5 KBheddn

Comments

trigdog created an issue. See original summary.

trigdog’s picture

Title: Handle fail exports better » Handle failed exports better
heddn’s picture

I think if we get an error, we could mark the row differently in SoapService->callReceiveResponseXML(). Or more specifically, updateIdentifier

trigdog’s picture

Great, I will look at that and work on something.

heddn’s picture

Status: Active » Needs review
StatusFileSize
new1.5 KB

  • heddn committed 70c24ed on 8.x-2.x
    Issue #2943362 by heddn: Handle failed exports better
    
heddn’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.