Hi, we have an issue which occurs when our customers daily sync from PIM to EPi is running. Almost all of the products are imported just fine, but lately a specific product has coused the import to fail. It happens when ne NodeEntry-relation is about to be set, which i find very strange. Other entries with relation to the same node is working perfectly fine. The error we receive from The Service API:
{"TimestampUtc":"2018-11-28T22:34:15.5474666Z","MessageType":5,"Message":"This row has been removed from a table and does not have any data. BeginEdit() will allow creation of new data in this row.","StageName":"Exception","StageIndex":1,"StageCount":1,"StageProgress":1,"StageTotalProgress":1,"ExceptionMessage":"This row has been removed from a table and does not have any data. BeginEdit() will allow creation of new data in this row.","ExceptionStackTrace":" at System.Data.DataRow.GetDefaultRecord()\r\n at System.Data.DataRow.get_Item(DataColumn column)\r\n at Mediachase.Commerce.Catalog.Dto.CatalogRelationDto.NodeEntryRelationRow.get_IsPrimary()\r\n at Mediachase.Commerce.Catalog.ImportExport.Import.NodeEntryRelationsReader.Read(ImportCatalogNodeCache relationCache)\r\n at Mediachase.Commerce.Catalog.ImportExport.Import.RelationsReader.Read(ImportCatalogNodeCache relationCache)\r\n at Mediachase.Commerce.Catalog.ImportExport.Import.Importer.Import(Stream stream, String sourceDirectory, Boolean overwrite)\r\n at Mediachase.Commerce.Catalog.ImportExport.CatalogImportExport.Import(String directoryPath, Boolean overwrite)\r\n at EPiServer.ServiceApi.Commerce.Jobs.CatalogImportJob.ExecuteJob(Guid jobId)"}
The relation XML-node from Import XML which fail:
<NodeEntryRelation><EntryCode>9723223</EntryCode><NodeCode>moj99lzdhusy</NodeCode><SortOrder>0</SortOrder><IsPrimary>True</IsPrimary></NodeEntryRelation>
This however, which is the Noderelation just above in the XML does work:
<NodeEntryRelation><EntryCode>9723197</EntryCode><NodeCode>moj99lzdhusy</NodeCode><SortOrder>0</SortOrder><IsPrimary>True</IsPrimary></NodeEntryRelation>
What happens to the relation that fails is that the Enty is placed on ROOT in the catalog with no relations. Any idea what could be cousing this behaviour? We are running EPiServer Commerce 12.5 and Service API 5.1