Calling all developers! We invite you to provide your input on Feature Experimentation by completing this brief survey.
Calling all developers! We invite you to provide your input on Feature Experimentation by completing this brief survey.
Hi Mark,
I think we can published only saved content, so you can modify saveAction as following and then try:
ContentVersion product = _contentRepository.Get<ProductType>(latestVersion.ContentLink);
if (product != null)
{
var clone = product.CreateWritableClone();
SaveAction saveAction= (product as IVersionable).Status == VersionStatus.Published
? SaveAction.Save | SaveAction.SkipValidation | SaveAction.ForceNewVersion | SaveAction.Publish;
: SaveAction.Save | SaveAction.SkipValidation | SaveAction.ForceCurrentVersion;
_contentRepository.Save(clone , saveAction, AccessLevel.NoAccess);
}
looks like the error is within the products published with the previous version, and within service API, Maybe you have to raise a bug with the support
Hi Mark,
Is it possible the products that are throwing an error are in the middle of a CMS approval sequence workflow?
Thanks
Episerver Commerce Version: 12.x
ServiceAPI Endpoint: episerverapi/commerce/entries/
Steps done to investigate
- Manual hit to endpoint with same payload, turns out to be working
We have episerver integration that calls episerver serviceAPI, at some point we encounter some data not updated. I found out that serviceAPI is failing, not all calls are failing.