The Property Mapper editor’s Advanced tab lets you map source properties to either Endeca properties or dimensions if no mapping is found.
The Property Mapper editor's Advanced tab contains the following option:
This option defines the default that Forge uses to handle source
properties that have neither explicit nor implicit mappings. There are three
possible settings:
- Uncheck the option altogether to ignore source properties that do not have an explicit or implicit mapping defined.
- Check Property to create a mapping between the source property and an Endeca property. Forge does this by creating a new Endeca property that uses the same name and value as the source property and assigning it to the record.
- Check Dimension to create a mapping between the source property and a dimension. Forge does this by creating a new dimension, using the source property's name. Forge uses the Auto Generate mode to populate the dimension with dimension values that match the source property's values.
Use the default mapping option with caution because:
- With this option enabled, all source properties will ultimately be mapped and mapped properties use system resources. Ideally, you should only map source properties that you intend to use in your implementation so that you minimize the use of system resources.
- Many production-level implementations automatically pull and process new data when it is available. If this data has new source properties, these properties will be mapped and included in your MDEX Engine indices. Again, this uses system resources unnecessarily but, perhaps more importantly, this situation may also result in the display of dimensions or Endeca properties that you do not want your users to see.
