Try our conversational search powered by Generative AI!
AI OnAI Off
Episerver ServiceAPI Error
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);
}
Edited,
Nov 22, 2021 8:21
Mark Malinao
- Nov 22, 2021 8:28
Hi @Sanjay,
We don't have save code, we call the ServiceAPI Endpoint at our integration code.
public static readonly string Entries = "/episerverapi/commerce/entries";
public EntryUpdateResult Update(Entry entry)
{
using (_performanceCounter.CreateScope(ScopeType.EntryUpdate))
{
ThrowIf.Null(entry, nameof(entry));
string uri = $"{_baseUri}/{entry.Code}";
HttpContent content = HttpUtil.GetJsonStringContent(entry);
HttpResponseMessage response = _serviceApiClient.Put(uri, content);
if (response.IsSuccessStatusCode)
{
return EntryUpdateResult.Success();
}
string message = response.Content.ReadAsStringAsync().Result;
return EntryUpdateResult.Failure(message);
}
}
We don't have save code, we call the ServiceAPI Endpoint at our integration code.
public static readonly string Entries = "/episerverapi/commerce/entries";
public EntryUpdateResult Update(Entry entry)
{
using (_performanceCounter.CreateScope(ScopeType.EntryUpdate))
{
ThrowIf.Null(entry, nameof(entry));
string uri = $"{_baseUri}/{entry.Code}";
HttpContent content = HttpUtil.GetJsonStringContent(entry);
HttpResponseMessage response = _serviceApiClient.Put(uri, content);
if (response.IsSuccessStatusCode)
{
return EntryUpdateResult.Success();
}
string message = response.Content.ReadAsStringAsync().Result;
return EntryUpdateResult.Failure(message);
}
}
Sanjay Kumar
- Nov 23, 2021 19:22
I can see you are following similar approach as mention in documents, so report the but to support.
https://world.optimizely.com/documentation/developer-guides/Optimizely-Service-API/catalog-restful-operations/Catalog-entries/#PutEntry
https://world.optimizely.com/documentation/developer-guides/Optimizely-Service-API/catalog-restful-operations/Catalog-entries/#PutEntry
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
Nov 22, 2021 9:58
Hi Mark,
Is it possible the products that are throwing an error are in the middle of a CMS approval sequence workflow?
Thanks
Nov 22, 2021 12:45
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.