Saving Specific Records in Experience Manager RecordSpotlight Cartridges Saves Aggregate Keys By Default, Rather Than Unique Record Specifiers
Last updated on MAY 15, 2017
Applies to:Oracle Commerce Platform - Version 10.0.2 and later
Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 3.1.0 and later
Information in this document applies to any platform.
Selecting RecordSpotlight "Specific Records", then clicking "Save" results in unexpected versions of an aggregate record being returned.
The specific version of the record that was originally selected is not honored, and a different representative record from the aggregate key may be shown.
In the Selected Records box within the Cartridge Editor, the unique record specifier is not shown.
Instead, the aggregate roll-up key is shown.
In the CRS application, by default, the unique Endeca record specifier is record.id. The roll-up key for aggregate records defaults to product.repositoryId.
In the internationalized version, this issue is most evident. Several records (SKUs) exist per-product.
There may be multiple SKUs for a single product if the product is sold in multiple languages, for instance.
To limit the records for selection to English only, the product.language "English" refinement is clicked.
The "Chair with a view dining chair" record is selected.
This has a unique record specifier of product-xprod2159..homeStoreCatalog.en__US.plist3080003__plist3080002
"Save Selection" is clicked.
Within the editor box, under the radios for "Specific Records" and "Records Selected By Query", only xprod2159 is shown as saved.
This value is the product.repositoryId for the selected record.
Navigating back to the "Edit List" modal, and reviewing the "Selected Records" tab, we see that the record is present in its German-language form:
product.displayName : Stuhl mit Aussicht
record.id : product-xprod2159..homeStoreCatalog.de__DE.plist3080003__plist3080002
This is because, by default, this particular aggregate record has the German version as its representative record.
If this issue started occurring suddenly on an environment with no other issues,
It is possible that a new aggregate record property was chosen in the Oracle Commerce Platform configuration settings.
If this aggregate property was previously undefined, or if it was not defined as the default "product.repositoryId", then until this point the Spotlight cartridges would be utilizing the unique record specifiers in this environment.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms