Hi The_Doc
The 500/504 errors have been an issue as mentioned for the past couple of weeks when updating the ItemPriceMatrix between the hours of 11pm and 4am. My first post shows the error log from our API application. When updating the prices, we need to GET all 5500+ items
The 409 error is due to a duplicate key for the ItemPriceMatrix and when we do a GET the incorrect RowVersion is returned preventing the prices from being updated.
We see different issues depending on how we update prices.
- 3rd Party App TransPost doesn't allow us to update prices at all. It causes all items to return an error 409
- MYOB File Import doesn't return any errors. If an item is affected by the duplicate key and you are importing new qty and/or price breaks it will import the prices as 0.00 (qty breaks are ok) or if there are existing prices they just don't update.
The API application we use (written in python) is the most reliable. We know exactly what was and wasn't updated and doesn't break the pricing for ALL items like TransPost or set prices to zero like the AccountRight file import.
If we see 409 errors in the logs, all we can do is update the prices manually and then ask support to run the "Item Price Matrix" script. Getting the script run is the issue. Forums post takes days to get the script run and live chat or phone you are on hold for hours sometimes. Please as we run the price updates at night its then 24 hours before the next update is run and we have prices between eCommerce and AccountRight that are out of sync.
This is the response we got from the API team on the issue
We had a discussion about this earlier in the morning.
The issue is with our devs and have advised the issue is in two parts.
- The item price matrix has duplicate data "stuck" in the table
- The API is displaying the "stuck" incorrect data
We will have to wait for a couple updates and hopefully have something implemented to be permanent across the board.
Until then we only have the script that can fix any edits that come with this problem.
What I don't understand is why there is NO importance to address the issue.
It has the potential, especially when using the AccountRight File Import to load a $0.00 price or not update a price at all, therefore, affecting a customer's business.