Hi Evdin,
I guest this issue could be Catalog Name at catalog level is not existed in database then this catalog is added to database before importing node content. But the catalog id that used for imporitng node is not assigned again after saving new catalog to database.
Could you please confirm if that is your case? You could report a bug if it is the exact case that you are facing.
Hello and thank you very much for your reply.
No, the catalog exists and is there with that given name. After doing some research (to be read that I banged my head against the wall), I discovered few things:
a) the import flow is very strange and the error message doesn't help at all - analyzing the order of the import steps I discovered that the issue might be in a total different place because the catalog itself wasn't analyzed from the XML point of view and the import process started directly with the node import.
b) the actual issue is just the fact that the XML it misses one line - please don't laugh but it's true - this is why the deserialization it's going nuts.
<?xml version="1.0" encoding="utf-8"?>
c) another important thing that it's not very well emphasized in the documentation is that, in order to have the existing catalog correctly identified, to have this node in your xml as a child for the catalog node:
<Languages>
<Language>
<LanguageCode>en</LanguageCode>
<UriSegment>xxx</UriSegment>
</Language>
</Languages>
Yes, that was it!!! Pretty simple but the errors are so wrongly served... :-(
Thank you again,
Evdin
Hello,
I'm having a very ugly situation and I cannot find any kind of clue where the issue might be.
In few simple words, I'm trying to import a very basic XML having this structure:
The problem is pretty simple - I'm getting the following log messages:
I connected to the development SQL server and I started the profiler in order to see what is being inserted in the CatalogNode table that generates the error and is pretty simple - the CatalogId is sent having the value 0.
I want to emphasize from the beginning that the catalog specified in the name attribute of the Catalog node exists and it has no problems.
I'm using the latest Commerce nuget packages:
EPiServer.Commerce: 14.22.0
EPiServer.ServiceApi: 7.1.0
EPiServer.ServiceApi.Commerce: 7.1.0
I don't understand what are the properties that are being used in order to identify the correct catalog where to insert the correct nodes.
Please, does anyone have any ideas?
Thank you,
Evdin