A breaking change was made for
LPS-103224, and an example came up recently in our internal slack: If you were using the DDM fields affected by LPS-103224 in a custom filter or custom facet, upgrading to 7.3 with these configurations breaks the functionality of the widget.
Things to cover on the Search side:
Now that we have features that require end users to look at and copy text from the mappings (custom facet, custom filter), we should probably add a warning, at least to the upgrade guide, and possibly to the documentation for each feature, that it's important to investigate changes to the breaking changes document for mappings changes if a custom filter or custom facet configuration stops working after an upgrade. In addition, we should document how to do this the new way or how to revert the indexing behavior for DDM (see below):
Things to cover on the DDM side (or maybe it's the Search side too, since it might only affect our search widgets):
There's a DDM System Setting to recover the legacy indexing behavior for the DDM fields. Explain how to do it and the danger of doing so (see