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:
- 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.
- 3100 - The name "Conserve Water Educators Guide" of the list element is already in use.
- 3180 - There was an error when saving a Item Inventory list, element "TEST PRODUCT". QuickBooks error message: An income account must be specified.
- 3000 - The given object ID "933498f4-1bd7-4db1-92f6-47cd5cf67745" in the field "list id" is invalid.
- 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.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 2943362.patch | 1.5 KB | heddn |
Comments
Comment #2
trigdog commentedComment #3
heddnI think if we get an error, we could mark the row differently in
SoapService->callReceiveResponseXML(). Or more specifically,updateIdentifierComment #4
trigdog commentedGreat, I will look at that and work on something.
Comment #5
heddnComment #7
heddn