Defining Receive MDM schema

Before you begin

This section describes how to define a receive MDM XML schema based on the MDM connection.

To set the XML schema you want to receive in accordance with a specific MDM connection, complete the following:

Procedure

In the Repository tree view, expand Metadata and right-click the MDM connection for which you want to retrieve the entity values, and select Retrieve Entity from the contextual menu.
In the MDM Model dialog box, select the Receive MDM option in order to define a receive XML schema and then click Next to proceed to the following step.
From the Entities field, select the business entity (XML schema) according to which you want to receive the XML schema.
The name displays automatically in the Name field.

Information noteNote: You can enter any text in this field, although you would likely put the name of the entity according to which you want to receive the XML schema.
Click Next to proceed to the next step.
The schema of the entity you selected display in the Source Schema panel. Here, you can set the parameters to be taken into account for the XML schema definition.

Example
The schema dialog box is divided into four different panels as follows:
- Source Schema: tree view of the uploaded entity.
- Target schema: extraction and iteration information.
- Preview: target schema preview.
- File viewer: raw data viewer.
In the Xpath loop expression area, enter the absolute XPath expression leading to the XML structure node on which to apply the iteration. Or, drop the node from the source schema to the target schema Xpath field. This link is orange in color.

Information noteNote: The Xpath loop expression field is compulsory.

If required, define a Loop limit to restrict the iteration to one or more nodes.

Example

In the above capture, Features is used as the element to loop on because it is repeated within the Product entity as the following:

<Product>
                            <Id>1</Id>
                            <Name>Cup</Name>
                            <Description/>
                            <Features>
                            <Feature>Color red</Feature>
                            <Feature>Size maxi</Feature
                            <Features>
                            ...
                            </Product>
                            <Product>
                            <Id>2</Id>
                            <Name>Cup</Name>
                            <Description/>
                            <Features>
                            <Feature>Color blue</Feature>
                            <Feature>Thermos</Feature>
                            <Features>
                            ...
                            </Product>

By doing so, the tMDMReceive component that uses this MDM connection will create a new row for every item with different feature.

To define the fields to receive, drop the relevant node from the source schema to the Relative or absolute XPath expression field.

Information noteTip: Use the plus sign to add rows to the table and select as many fields to extract as necessary. Press the Ctrl or the Shift keys for multiple selection of grouped or separate nodes and drop them to the table.
If required, enter a name to each of the received columns in the Column name field.

Information noteTip: You can prioritize the order of the fields you want to receive by selecting the field and using the up and down arrows. The link of the selected field is blue, and all other links are grey.
Click Finish to validate your modifications and close the dialog box.

Results

The newly created schema is listed under the corresponding MDM connection in the Repository tree view. You can modify the created schema according to your needs and drop the connection as a tMDMReceive in any of your Jobs.

For more information on how to modify the schema, see Modifying the created schema.

Newly created schema appeared in the Repository tree view.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here