Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Retrieve entity values for an MDM connection

Last updated: 5/18/2026

About this task

To set the values to be fetched from one or more entities linked to a specific MDM connection, complete the following:

Procedure

  1. 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.

    Example

    Retrieve Entity option selected by right-clicking.
  2. In the MDM Model dialog box, select the Input MDM option in order to download an input XML schema and then click Next to proceed to the following step.
  3. From the Entities field, select the business entity (XML schema) from which you want to retrieve values.
    The name is displayed automatically in the Name field.

    Example

    Information noteNote: You are free to enter any text in this field, although you would likely put the name of the entity from which you are retrieving the schema.
  4. Click Next to proceed to the next step.
    The schema of the entity you selected is automatically displayed in the Source Schema panel. Here, you can set the parameters to be taken into account for the XML schema definition.

    Example

    MDM Entity dialog box showing schema.
    The schema dialog box is divided into four different panels as follows:
    • Source Schema shows the tree view of the uploaded entity.
    • Target schema shows the extraction and iteration information.
    • Preview shows the target schema preview.
    • File viewer shows the raw data.
  5. 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.
  6. If required, define a Loop limit to restrict the iteration to a number of nodes.

    Example

    "Features" used as a loop.

    Example

    In the capture above, Features is used as the element to loop on because it is repeated within the Product entity as follows:
    <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 tMDMInput component that uses this MDM connection will create a new row for every item with different feature.
  7. To define the fields to extract, drop the relevant node from the source schema to the Relative or absolute XPath expression field.

    Example

    Source Schema elements linked to Relative or absolute XPath expression.
    Information noteTip: Use the [+] button 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.
  8. If required, enter a name to each of the retrieved columns in the Column name field.
    Information noteTip: You can prioritize the order of the fields to extract 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.
  9. 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.
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