Sales Item / Service incorrect
Hi, I have developed a small application that pulls data using the API to generate a timber cut list for a client. This has been working fine until recently where I have found that I am missing ...
Forum Discussion
I am experiencing a nearly identical issue with Purchases. Within the MYOB application, it is an Item Purchase Order with an item line, but through the API it does not come through the ItemPurchaseService, it comes through the ServicePurchaseService.. and as the original poster mentions, the lines from the API do not contain item codes because the API believes it is a ServicePurchase. In addition, it also comes through the generic PurchaseService, but with order type "Service".
I need access to the Item Lines.
All other Item Purchase Orders come through correctly, not sure why the API believes this particular Purchase is a Service Purchase.
Have a look at this thread and see if it is of any use (even if it only confirms the problem).
Hi John.. Thanks for the link... Last week, I stumbled across the issue you bring up on that post, but as you mention, it's a simply fact of ignoring it. In other words, I assumed that the ItemPurchase endpoint returning ItemPurchase objects with the status of Service was just a bug.. This did not prevent me from using the ItemPurchaseLines as they were all correct. So even though, the ItemPurchase had a status of "Service", this was easy enough to ignore and still do work we required. I have no trouble processing the majority of our purchases.
The issue I am describing, and also described on the post by the poster that you link is a different issue than just an incorrect status. Namely, no purchase is returned when querying the ItemPurchase Endpoint for a specific item purchase. The only way to get the purchase, is by querying the ServicePurchase endpoint, or the Purchase endpoint.. both of which don't give you lines you can use.. I am yet to find the specific conditions for a purchase to get incorrectly placed via endpoint... funnily enough, after conversion to bill, it then gets correctly positioned, in other words, i can successfully get it from the ItemBill endpoint.
Ah ok. So you are having this problem with one particular Item Purchase Order and not all of them is that correct?
I am using the SDK/API and am able to return an Item Purchase Order (and its lines) using the ItemPurchaseOrderService and ItemPurchaseOrderSvc.GetRange with this filter (e.g.):
$filter = Number eq '00000012'
I have not noticed it fail yet, but that doesn't necessily mean that it hasn't.
