Adding new leaf dimension values in partial updates

This section describes one method of adding new leaf dimension values for existing dimensions in partial updates. In partial updates, you can create new leaf dimension values. (You cannot add new dimensions or new mid-hierarchy dimension values.)

Before adding a new leaf dimension value, ensure that a dimension already exists in your record set for the leaf dimension value. For example, if you are planning to add a record with a new leaf dimension value of “Australia”, ensure that a dimension “region” is already specified for your records.

To do this, in your baseline update pipeline, add a new dimension in the Dimension editor in Developer Studio, and select the Auto Generate mode in the Property Mapper editor. This generates dimension values for the dimension. Run a baseline update.

In order to add leaf dimension values, you can use the Property Mapper editor option to automatically generate new values for existing dimensions.

To add a new leaf dimension value in a partial update:

  1. Add a new record to your record set that includes a leaf dimension value for the dimension that already exists in your project (and that was added before).
  2. Modify the record manipulator to indicate that you are updating dimension values. Use the UPDATE_RECORD expression with <EXPRNODE NAME="DIM_ACTION" VALUE="ADD"/>.
  3. Run a partial update. The newly added leaf dimension value is added to the project during a partial update.

For example, when you add a new record that has a value “Australia”, the partial update generates a new value for region=”Australia” when the new record goes through the property mapper in the partial update pipeline.

The output XML files in Forge that result from the partial update include the new record, as well as the new dimension value for it. When the Dgraph is updated with that file, it includes the new record, as well as the new dimension value of “Australia”.