Hi Paul,
I don't believe that is standard behaviour. Try inspecting the [InventoryService] table. Maybe you're not providing one of the mandatory fields?
inventory system is fairly independent from the catalog, it only needs the entry with the code exists. what error message are you seeing?
@Paul - how do you send the data and how do you check to see if it's updated ? sounds like a cache somewhere
does it work if you update inventories for published content?
if (!_catalogRepository.EntryExists(warehouseInventory.CatalogEntryCode))
this catches my eyes. can you check if this does not check for publish status?
Unless you are sure that each run will only update inventories of each sku in one warehouse, you can speed up quite a lot by updating all inventories of same sku in one go
Something is wrong somewhere else. if you are using the Catalog UI to update inventory in a Ready to Publish content, does it persist? because your code is essentially what Catalog UI does under the hood
Something is wrong somewhere else. if you are using the Catalog UI to update inventory in a Ready to Publish content, does it persist? because your code is essentially what Catalog UI does under the hood
Hi,
We are currently investigating an issue with the state 'Ready To Publish' upon a catalog entry item.
We have an api that updates the inventory for the catalog entry however it appears to not be doing this when the item is set to 'Ready to Publish'.
Does anyone know if that behaviour is correct?
Thanks