Verify that your mappings are properly configured, and that you have correctly enabled property and dimension display. For projects that use MDEX prior to 6.1.0, verify that precedence rules connect any manually-set primary dimensions to secondary dimensions.
If a source property does not appear correctly in your Endeca-enabled Web application, make sure that:
Your source property is mapped to either an Endeca property or a dimension in your pipeline's property mapper. See Establishing a property mapping and Establishing a dimension mapping for details.
If the source property is mapped to a dimension, the dimension is either configured for auto-generation, or the source property values on the records match the dimension values that you explicitly defined for the dimension in the Dimensions editor.
The Show with Record List and Show with Record options are set correctly in the Property editor or Dimensions editor. See one of the following sections for details:
In releases prior to the MDEX Engine v.6.1.0, if you had manually designated a primary dimension, you had to create precedence rules from that dimension to all of your secondary dimensions. If you are using Developer Studio with the MDEX Engine v.6.1.0 and up, you no longer have to create precedence rules from the primary dimension to all your secondary dimensions. Primary dimension is also no longer requiredor used by the MDEX Engine.
