Retrieving customised inventory prices in bulk

[Mike.Sheen]

hence my suggestion it might be the side effect of another plugin

That's my first instinct after reading this topic.

@mls you could try as a test against our public https://api.jiwa.com.au demo API - do you get the error when POSTing there?

[SBarnes]

I have been there and done that.
And NO you don't.

[Mike.Sheen]

I have been there and done that.
And NO you don't.

[mls]

@Mike The Jiwa test API is working for me

[mls]

Update: the problem has now been resolved. Turns out the error message above was very misleading...we finally realised after some detailed troubleshooting that the error was caused by incorrect API user group permissions.

[Mike.Sheen]

Update: the problem has now been resolved. Turns out the error message above was very misleading...we finally realised after some detailed troubleshooting that the error was caused by incorrect API user group permissions.

So - in order for us to improve the message, how would I go about reproducing the issue?

[mls]

Update: the problem has now been resolved. Turns out the error message above was very misleading...we finally realised after some detailed troubleshooting that the error was caused by incorrect API user group permissions.

So - in order for us to improve the message, how would I go about reproducing the issue?

I'm waiting to get clarification on that from the person who manages our Jiwa installation. Will let you know when I get a reply.

[mls]

I have some more questions about creating stateful Sales Quotes/Orders to retrieve customised inventory prices in bulk.

Is there any reason to use Sales Quotes rather than Sales Orders (or vice versa)? Or would both work equally well to solve this problem?

Are there any reasons why a request might fail? Perhaps if some of the inventory items are unavailable, or...?

If we end up using this solution, we will be creating a large number of stateful objects...basically every time a customer loads a new page of product listings on the website. How likely is this to cause a problem inside Jiwa? I'm thinking we should be ok if we free up memory by abandoning the Quote/Order immediately after creating it...does that make sense?

[Mike.Sheen]

Is there any reason to use Sales Quotes rather than Sales Orders (or vice versa)? Or would both work equally well to solve this problem?

Sales orders will take the stock and make it unavailable to other orders or uses - except if the sales order is a type Forward Order - sales quotes on the other hand, won't take the stock.
If you use sales orders and set it as a Forward order, then it's the same practically as quotes.

Are there any reasons why a request might fail? Perhaps if some of the inventory items are unavailable, or...?

Not really - if a sales order is not a forward order, and you don't have enough stock AND the item(s) are not backorderable items, then you may have a problem setting the quantity - but I'm pretty sure it just adjusts the quantity down and does not throw an exception.[/quote]

If we end up using this solution, we will be creating a large number of stateful objects...basically every time a customer loads a new page of product listings on the website. How likely is this to cause a problem inside Jiwa? I'm thinking we should be ok if we free up memory by abandoning the Quote/Order immediately after creating it...does that make sense?

We've actually removed stateful from the next major release of Jiwa (what will be Version 8) - I think you may now want to steer away from that as a solution.

[mls]

We've actually removed stateful from the next major release of Jiwa (what will be Version 8) - I think you may now want to steer away from that as a solution.

Ah. So it seems that my options are:

- fetch priced items one by one
- create/delete stateless Sales Quotes ad hoc
- create a Jiwa plugin to return prices in bulk

Is that correct?