Changing documents and root element

You can update or change the input or output schema, or document root elements of a mapping. The progress and result of this action are logged in the Mapping Console view. If the input or output schema contains a wildcard node, then remove first the replacement element before changing documents.

See Removing replacement elements.

Note: If you change documents for a customized BOD mapping, then the input and output root element names must not be changed. The mapping properties SchemaIn.Category and SchemaOut.Category must not be changed either. If these mapping properties are changed, then you cannot use the customized BOD mapping instead of the standard BOD mapping.
  1. In the Mapper Explorer view, right-click a mapping and select Change Documents.

    You must not open your selected mapping in the Mapping Editor. If open, then click OK to close the editor and proceed. The fields are automatically populated with default values.

  2. Click Browse for a specific field to change the default value. Specify this information:

    The current project name is the default value.

    Copy or Overwrite

    Optionally, select Copy or Overwrite to select how to apply your changes. Copy is the default selection.

    Mapping Name

    Specify a new name for the mapping. The mapping name must be a valid Java class name.

    • This is a potentially risky operation so your current mapping should be preserved. When Copy is selected, a new mapping folder is created by copying your current mapping and applying the changes on the mapping with new name.
    • When Overwrite is selected, the current mapping is overwritten and not preserved.
    Input schema

    Specify a new input schema, or accept the default value.

    Output schema

    Specify a new output schema, or accept the default value.

  3. Click Next.
  4. Select the root elements for the input or output tree.
  5. Click Finish.

    The new mapping opens in a new tab in the Mapping Editor. Document elements linked to mapping elements may not be displayed if the new schemas have different content as compared to the old ones. The difference in schema content results in an inconsistent mapping with broken links. The new mapping is a custom mapping.