Don't miss out Virtual Happy Hour this Friday (April 26).
Try our conversational search powered by Generative AI!
AI OnAI Off
"An item with the same key has already been added" in contentLoader.GetChildren<T>(contentLink)
Can you share code. Specially the extension method around line 157 in ContentReferenceExtension.cs (last line in your stack trace).
Nov 15, 2019 3:02
Have you run sql profiler and catched the stored procedure call for "CatalogContentProperty_LoadBatch"?
If you run that call against the database, what result do you get?
Nov 15, 2019 14:20
Line 157 is:
var items = contentLoader.GetChildren<T>(contentLink).ToList();
Nov 15, 2019 15:18
What we found last night and early this morning indicates that we somehow have meta fields that have culture-specific values, but they're marked as not culture-specific, so when the meta data is gathered together, Epi attempts to add multiple values for the same field to the gathered object. Still digging into how many products are in this state and how they may have gotten that way.
Nov 15, 2019 15:33
It is possible that your CatalogContentProperty have duplicated rows with same ObjectId, ObjectTypeId, LanguageName and MetaFieldName
This should return those duplicated rows:
select objectid, objecttypeid, languagename, metafieldname
from CatalogContentProperty
group by objectid, objecttypeid, languagename, metafieldname
having count(*) > 1
You are of course welcome to contact developer support service for further assistance
Nov 15, 2019 16:23
Quan, that's what we thought might be the problem too, but there aren't any actual duplicates of that kind.
I did also put in a ticket with support, but posted here because sometimes other users have found problems and solutions that the official support hasn't seen.
Nov 15, 2019 16:54
Quan, that's what we thought might be the problem too, but there aren't any actual duplicates of that kind.
I did also put in a ticket with support, but posted here because sometimes other users have found problems and solutions that the official support hasn't seen.
Nov 15, 2019 16:54
It's good that you contacted developer support service. We might need to look into your database to see what is in there ..
Nov 18, 2019 9:59
I also had this issue and ran this query to identify mismatches between culture specific metafields and not culture specific property values for those metafields:
SELECT
[ObjectId],
[MetaFieldName],
CCP.[MetaFieldId],
[LanguageName],
[CultureSpecific],
MF.[MultiLanguageValue]
FROM CatalogContentProperty CCP
INNER JOIN MetaField MF ON MF.MetaFieldId = CCP.MetaFieldId
where [CultureSpecific] = 0
and MF.[MultiLanguageValue] = 1The solution was to run this query to fix the issue:
UPDATE CatalogContentProperty
SET [CultureSpecific] = 1
WHERE [CultureSpecific] = 0
AND [MetaFieldId] IN (
SELECT DISTINCT
CCP.[MetaFieldId]
FROM CatalogContentProperty CCP
INNER JOIN MetaField MF ON MF.MetaFieldId = CCP.MetaFieldId
WHERE [CultureSpecific] = 0
AND MF.[MultiLanguageValue] = 1
)
Feb 06, 2020 11:00
Quan Mai
- Feb 06, 2020 11:08
UPDATE CatalogContentProperty
SET [CultureSpecific] = 1
WHERE [CultureSpecific] = 0
AND [MetaFieldId] IN (
SELECT MetaFieldId
FROM
MetaField MF
WHERE MF.[MultiLanguageValue] = 1
)
it can be simplified. I don't know why you have the mismatches however
SET [CultureSpecific] = 1
WHERE [CultureSpecific] = 0
AND [MetaFieldId] IN (
SELECT MetaFieldId
FROM
MetaField MF
WHERE MF.[MultiLanguageValue] = 1
)
it can be simplified. I don't know why you have the mismatches however
Mattias Olsson
- Feb 06, 2020 11:14
It doesn't have to be simplified. I run it once, done. ;) But yeah, I agree that your script is better. :)
I don't know about the mismatches either.
I don't know about the mismatches either.
Mattias Olsson
- Feb 06, 2020 13:12
@Quan Mai: What if a metafield, at some point, is changed from non multilanguage to multilanguage, will data in CatalogContentProperty auto heal then?
Mattias Olsson
- Feb 06, 2020 13:17
In our case, we use InRiver. So all data is basically in a catalog XML file and sent to the importer.
Epi version: 11.11.3.0
Commerce version: 12.17.2.0
We have some catalog categories that are throwing "An item with the same key has already been added" exceptions when we attempt to GetChildren on the category's contentLink. The categories in question work for the en-us culture, but the en-ca versions are blowing up. The <T> in question is our product interface. Our categories can have subcategories and the retrieval of those children works, but the product children causes that Epi call to fail.
Clearly, something is corrupt/misconfigured about those products, but I'm trying to figure out what it is (which will hopefully help me track down how it happened and prevent it in the future). Even if I could just know what key is duplicated, it might be helpful.
Partial stack trace (for some reason, the full one won't submit):