Sep 18, 2019
Mar 20, 2020
Closed, Fixed and tested
Steps to reproduce
The expected result would be to have Books$$nested and Books2$$nested in all listed indices.
The actual result is that only Books$$nested exist.
We are only checking if any mapping exists in any index for the document type NestedDummyObject$$nested, whereas we need to check if the named object field has a mapping in the document type NestedDummyObject$$nested.
To be a bit more specific: the if clause in EPiServer.Find.ClientConventions.NestedConventions.AddNestedType() on line 155 does not check what we would expect it to.
Any customer that runs Find API 13.2.X with a clean index gets incomplete mappings for nested objects. This affects all customers being migrated to V3.
I am not sure about the ramifications of the missing mappings, but we may get shard failures when using nested facets and sorting.