Baseline Update Generates Multiple Price Dimensions When One Range Dimension Is Required
(Doc ID 2298163.1)
Last updated on SEPTEMBER 14, 2017
Applies to:Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 6.1.0 and later
Information in this document applies to any platform.
A dimension is not being sorted into its relevant range bounds when viewed on the Orange JSP Reference Application, nor on the front-end application.
Baseline indexing results in all price dimension values being auto-generated for a particular parent dimension (hierarchical price dimension).
This results in hundreds of individual price refinements under the Guided Navigation panel for the parent dimension.
These dimension values should have been added to predefined range dimensions, instead.
The issue can be reproduced at will with the following steps:
1. Add a new customer price list dimension (dimprice dimension value)
2. Define ranges for this dimension in a flat file that is to be used during data ingest
3. Run a baseline_update
4. See that, unlike the other dimprice dimensions, this new dimension's values are individual prices, rather than the defined ranges
Hierarchical dimension root: CustomerSpecificPricing
First children: customerCodePrice -- e.g. 123Price
Second children: Region-specific price ranges -- e.g. < $10, $11-$100, etc.
When the 123Price dimension value (refinement) is expanded in the refinement menu of the orange reference application, price ranges are seen:
< $10 (12)
When the newly added 234Price dimension value (refinement) is expanded in the refinement menu of the orange reference application, hundreds of individual price dimensions are seen:
A new dimension has been added.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document