There are a number of differences in the names of dimension value properties in Forge-based and CAS-based applications:

By default, the components that produce dimension value records (including the CategoryToDimensionOutputConfig, RepositoryTypeDimensionExporter, ArticleDimensionExporter, and MediaContentDimensionExporter components) output records whose property names reflect the older Forge-based deployment template. To support the naming conventions used with CAS-based deployment templates, the propertyNameReplacementMap property of the DimensionDocumentSubmitter component is used to map the older-style names to the new ones. By default, this property is set as follows:

propertyNameReplacementMap=\
  dimval.qualified_spec=Endeca.Id,\
  dimval.dimension_spec=dimval.dimension_name,\
  dimval.prop.category.ancestorCatalogIds=category.ancestorCatalogIds,\
  dimval.prop.category.rootCatalogId=category.rootCatalogId,\
  dimval.prop.displayName_es=displayName_es,\
  dimval.prop.displayName_en=displayName_en,\
  dimval.prop.displayName_de=displayName_de,\
  dimval.prop.category.repositoryId=category.repositoryId,\
  dimval.prop.category.catalogs.repositoryId=category.catalogs.repositoryId,\
  dimval.prop.category.siteId=category.siteId

So, for example, dimval.qualified_spec is renamed to Endeca.Id in the output records, dimval.dimension_spec is renamed to dimval.dimension_name, and dimval.prop.category.repositoryId is renamed to category.repositoryId.

For a Forge-based application, set the propertyNameReplacementMap property to null to restore the older-style names:

propertyNameReplacementMap^=/Constants.null

And set the idPropertyName property of the DimensionDocumentSubmitter component to dimval.qualified_spec:

idPropertyName=dimval.qualified_spec

Copyright © 1997, 2015 Oracle and/or its affiliates. All rights reserved. Legal Notices