When we export our catalog which has Svenska as primary language all metadatavalues that are not set as multilanguage is set to language="en".
Is there a way to control this?
Here's a good example of the error from the generated Catalog.xml:
ItemMaterial EnumMultiValue ItemName LongString
Multilanguage fields are correctly setting the sv values but non multilanguage fields are specified in en. This kind of ruins the whole import/export functionality because an environment setup using the exported data gets completely wrong.
Not sure which version you are working on - but is Svenska your catalog default language (master language)?
CMS v 9.8.2 Commerce 9.13.
Yes, Svenska is the catalogs default language that's what makes this so strange. I can't find any other setting that would affect this
Is there a chance that it was English but then you changed it to Svenska?
The catalog is generated by InRiver.
From InRiver the catalogspecification looks like this in the Catalog.xml that it generates:
<Catalog name="Web" lastmodified="2016-05-16 09:15:00" startDate="2016-05-30 02:27:16Z" endDate="2116-05-30 02:27:16Z" defaultCurrency="SEK" weightBase="kilogram" defaultLanguage="sv" sortOrder="0" isActive="True" languages="sv,en">
What do you have in database if you run this query against Commerce db:
Select * from dbo.CatalogContentProperty where MetaFieldName = ItemMaterial
Where ItemMeterial is the name of your field
Data like this
5448216 22518 0 429 47 ItemMaterial en NULL 69780 NULL NULL NULL NULL NULL NULL NULL NULL5448217 22518 0 429 47 ItemMaterial sv NULL 69779 NULL NULL NULL NULL NULL NULL NULL NULL5448218 22520 0 429 47 ItemMaterial en NULL 69782 NULL NULL NULL NULL NULL NULL NULL NULL5448219 22520 0 429 47 ItemMaterial sv NULL 69781 NULL NULL NULL NULL NULL NULL NULL NULL
Hmm - that's very strange.
I would suggest you to contact our developer support service. We'll need to investigate your database.
Or perhaps you can send me the catalog generated by inRiver so I can see if this is a bug or not. quma [at] episerver.com
It is registered as a support ticket. Unfortunately all exports from InRiver comes in small chunks so I don't have a good export file to send. But if needed I can send the database connetced to the support ticket.
So how was the catalog created?
It was created a while back but since InRiver sends all updates in small chunks we have had to implement a removal job that cleans the syncfolder every once and a while to keep it from bloating the folder. So therefor I only have small catalog.xml created for updating specific products and skus and not a complete syncing. But the InRiver sync hasn't been changed in a long time so I can't see that it would generate a different catalog.xml when the catalog was created a couple of weeks ago. We have had the catalog removed and recreated a couple of times before to handle changes in Meta data fields so it's a fairly new catalog that we run now and I'm almost certain that the language setting has been correct all the time.