We actually have a plan to move ServiceAPi to use content APIs internally, but that takes time and has not been prioritized, so it will take some time. I.e. it will not be implemented any time soon
Hello Quan Mai,
Thank you for the feedback. We can appreciate that this will not be a quick change.
Do you have a high level timeline? We have a customer (a large automotive brand) who has implemented a Service API solution, but require the versioning functionality for legal reasons, especially with eCommerce. A timeline will indicate to us whether they will have to invest in a workaround / temporary solution until Episerver prioritizes this feature.
We require an extension of the current Service API for Epi Commerce to allow for the versioning of products, SKUs and categories.
On update of an object, we need the ability to: