Forge2cas Utility Only Outputs DISPLAY Mapping Value When Multiple Synonyms Are Present On a Dimension Value (Doc ID 2247375.1)

Last updated on DECEMBER 09, 2024

Applies to:

Goal

When migrating from a Forge-based application to a CAS-based application and running the forge2cas utility, the [APP]-dval_id_mappings.csv file that gets created contains the incorrect dimension value mappings.  When there are multiple dimension value synonyms in a dimension value definition, like often found in an ATG integration, forge2cas only produces a mapping for the "DISPLAY" dimension value synonym and not the alternative synonym value that represents the ATG category data.  This causes invalid dimension value ID mappings to be created which can negatively affect Experience Manager location triggers and other refinement behaviors in the application.

For example, the following dimensions.xml file to be converted contains the following dimension value definition (excerpt), which contains multiple dimension value synonyms:

However, this is not the desired mapping to be produced.  The desired mapping should not be for the "display" synonym "Trainer", it should be for the other dimension value synonym entry which represents the ATG category data "cat12345.cat67890", which is a common way to map ATG data to Endeca dimensions.

How can the forge2cas utility be made to output the correct dimension value synonym mapping in the mapping csv file?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.