Issues with Product Availability Table (API)
This request relates to some challenges we're facing with product availability records on the DEAR API -
1. Is it possible to include a unique ID for each product availability (ref/productavailability) record? The records expose the associated Product ID, but no unique identifier for the record itself. Since Products can relate to many Product Availabilities, Product ID really isn't sufficient in our use case insofar as data integrity is concerned, and made worse by the fact that only the locations and bin names are exposed on the product availability record (i.e. no ID's).
2. The Product Availability table does not provide a "last modified on" field. Is it possible to include this (and importantly a "modified since" URI parameter) similar to the Product table? For our use case, Product Availability records across Location/Bin combinations will reach large multiples to be syncing en masse each time, it would be really useful to filter the requests by a modified date to drastically reduce the number of records needlessly processed each sync.
3 people like this idea