Logical Modeling

Logical modeling allows defining the business entities that make up the model.

Introduction to Logical Modeling

In Semarchy Convergence for MDM, modeling is performed at the logical level. You do not design physical objects such as tables in a model, but logical business entities independently from their implementation.

Logical Model Objects

Logical modeling includes creating the following objects:

In the modeling phase, integration processes objects such as Enrichers, Matchers and Consolidators are also created. Creating these objects is described in the Integration Process Design chapter. After completing the modeling phase, you can create Applications to access the data stored in your model.

Objects Naming Convention

When designing a logical model, it is necessary to enforce a naming convention to guarantee a good readability of the model and a clean implementation.
There are several names and labels used in the objects in Semarchy Convergence for MDM:

The following tips should be used for naming objects:

Model Validation

A model may be valid or invalid. An invalid model is a model that contains a number of design errors. When a model is invalid, you cannot deploy it, and you cannot close this model edition. Model validation detects errors or missing elements in the model. For example, entities with no consolidation strategies are detected.

To validate the model:

  1. In the Model Edition view of the Model Design Perspective, select the model node at the root of the tree. You can alternately select on entity to validate only this entity.
  2. Right-click and select Validate.
  3. The validation process starts. At the end of the process, the list of issues (errors and warnings) is displayed in the Validation Report view. You can click an error or waning to open the object causing this issue.

Tip: It is recommended to regularly run the validation on the model or on specific entities. Validation may guide you in the process of designing a model. You can perform regular validations to assess how complete the model really is, and you need to pass model validation before deploying or closing a model edition.

Generating the Model Documentation

When a model is complete or under development, it is possible to generate a documentation set for this model.

This documentation set may contain the following documents:

The documentation is generated in HTML format and supports hyperlink navigation within and between documents.

To generate the model documentation:

  1. In the Model Edition view of the Model Design Perspective, select the model node at the root of the tree.
  2. Right-click and select Export Model Documentation.
  3. In the Model Documentation Export dialog, select the documents to generate.
  4. Select the appropriate Encoding and Locale for the exported documentation. The local defines the language of the generated documentation.
  5. Click the Download link to download the documentation.

The documentation is exported in a zip file containing the selected documents.

Note: It is possible to export the model documentation only for a valid model.

Types

Several types can be used in the Semarchy Convergence for MDM models:

All these type as the user-defined are reused across the entire model.

Tip: A list of values, user-defined or complex type is designed in the model and can be used across the entire model. Changes performed to such a type impact the entities and attributes using this type. To list the attributes using a type and analyze the impact of changing a type, open the editor for this type and then select the Used in item in the left sidebar.

Built-in Types

Built-in types are provided out of the box in the platform.

Built-in types include:

List of Values

List of Values (LOVs) are a user-defined list of code and label pairs.
They are limited to 1,000 entries and can be imported from a Microsoft Excel Spreadsheet.

Examples:

Info: Lists of values are limited to 1,000 entries. If a list of value needs to contain more than 1,000 entries, you should consider implementing in the form of an entity instead.

To create a list of values:

  1. Right-click the List of Values node and select Add List of Values.... The Create New List of Values wizard opens.
  2. In the Create New List of Values wizard, check the Auto Fill option and then enter the following values:
  3. Click Finish to close the wizard. The List of Values editor opens.
  4. In the Description field, optionally enter a description for the user-defined type.
  5. Add values to the list using the following process:
    1. In the Values section, click the Add Value button. The Create New LOV Value dialog appears.
    2. In this dialog, enter the following values:
      • Code: Code of the LOV value. This code is the value stored in an entity attribute.
      • Label: User-friendly label displayed for a field having this value.
      • Description: Long description of this value.
    3. Click Finish to close the dialog.
  6. Repeat the previous operations to add the values. You can select a line in the list of value and click the Delete button to delete this line. Multiple line selection is also possible.
  7. Press CTRL+S to save the editor.
  8. Close the editor.

List of values can be entered manually as described above and can be translated as described in the Localization section of the Working with Model Display chapter.

In addition, you can also import values or translated values from a Microsoft Excel Spreadsheet.
This spreadsheet must contain only one sheet with three columns containing the Code, Label and Description values. Note that the first line of the spreadsheet will be ignored in the import process.

To import a list of values from an excel spreadsheet:

  1. Open the editor for the list of value.
  2. Expand the Values section.
  3. In the Values section, click the Import Values button. The Import LOV Values wizard appears.
  4. Use the Open button to select a Microsoft Excel spreadsheet.
  5. Choose the type of import:
  6. Click Next . The changes to perform are computed and a report of object changes is displayed.
  7. Click Finish to perform the import. The Import LOV wizard closes.
  8. Press CTRL+S to save the editor.
  9. Close the editor.

User-Defined Types

User-Defined Types (UDTs) are user restriction on a built-in type. They can be used as an alias to a built-in type, restricted to a given length/precision.

Examples:

To create a user-defined type:

  1. Right-click the User-defined Types node and select Add User-defined Type.... The Create New User-defined Type wizard opens.
  2. In the Create New User-defined Type wizard, check the Auto Fill option and then enter the following values:
  3. Click Finish to close the wizard. The User-defined Type editor opens.
  4. In the Description field, optionally enter a description for the user define type.
  5. Press CTRL+S to save the editor.
  6. Close the editor.

Complex Types

Complex Types are a customized composite type made of several Definition Attributes using Built-in Type, User-Defined Type or a List of Values.

For example, an Address complex type has the following definition attributes: Street Number, Street Name, Zip Code, City Name and Country.

To create a complex type:

  1. Right-click the Complex Types node and select Add Complex Type.... The Create New Complex Type wizard opens.
  2. In the Create New Complex Type wizard, check the Auto Fill option and then enter the following values:
  3. Click Finish to close the wizard. The Complex Type editor opens.
  4. In the Description field, optionally enter a description for the complex type.
  5. Select the Definition Attributes item in the editor sidebar.
  6. Repeat the following steps to add definition attributes to this complex type:
    1. Select the Add Definition Attribute... button. The Create New Definition Attribute wizard opens.
    2. In the Create New Definition Attribute wizard, check the Auto Fill option and then enter the following values:
      • Name: Internal name of the object.
      • Label: User-friendly label for this object. Note that as the Auto Fill box is checked, the Label is automatically filled in. Modifying this label is optional.
      • Physical Column Name: Name of the physical column containing the values for this attribute. This column name is prefixed with the value of the Physical Prefix specified on the entity complex attribute of this complex type.
      • Type: List of values, built-in or user-defined type of this complex attribute.
      • Length, Precision, Scale. Size for this definition attribute. The fields available depend on the built-in type selected. For example a String built-in type will only allow entering a Length. If a list of values or a user-defined type was selected, these values cannot be changed.
      • Mandatory: Check this box to make this definition attribute mandatory when the complex type is checked for mandatory values.
    3. Click Finish to close the wizard. The new definition attribute appears in the list. You can double-click the attribute in the list to edit it further and edit its advanced properties (see below).
  7. Press CTRL+S to save the Complex Type editor.
  8. Close the editor.

A complex type has the following advanced properties that impact its behavior:

Entities

Entities are the key components of the logical modeling. They are not database tables, but they represent Business Entities of the domain being implemented in the MDM Project. Example of entities: Customers, Contacts, Parties, etc.

Entity Characteristics

Entities have several key characteristics. They are made of Attributes, have a Matching Behavior and References. They also support Inheritance.

Attributes

Entities have a set of properties, called Attributes. These attributes can be either:

For example, the Contact entity may have the following attributes:

Matching Behavior

Each entity has a given a matching behavior. This matching behavior expresses how similar instances (duplicates) of this entity are detected:

Important: The choice of a Matching Behavior is important. Please take into account the following differentiators when creating an entity.

ID Matching

Use ID Matching only when there is a true unique identifier for all the applications communicating with the MDM Hub, or for simple data entry use cases.

Fuzzy Matchings

Use Fuzzy Matching only when you do not have a “shared” identifier for all systems, or when you want to perform fuzzy matching and consolidation on the source data.

ID Generation
The matching behavior impacts the method used for generating the values for the Golden Record Primary Key:

Note: When generating IDs automatically using a Sequence in data entry forms for an ID Matching entity, you must take into account records pushed by other publishers (using for example a data integration tool). These publishers may use the same IDs for the same entity, and in this case the records will match by ID. If you want to separate records entered manually from other publishers' records and avoid unexpected matching, configure your sequence using the Start With option to start beyond the range of IDs used by the other publishers.

References

Entities are related using Reference Relationships. A reference relationship defines a relation between two entities. For example, an Employee is related to a CostCenter by a EmployeeHasCostCenter relation.

Constraints

Data quality rules are created in the design of an entity. These constraints include:

These constraints are checked on the source records and the consolidated records as part of the integration process. They can also be checked to enforce data quality in data entry workflows .

Inheritance

Entities can extend other entities (Inheritance). An entity (child) can be based on another entity (parent).
For example, the PersonParty and OrganizationParty entities inherit from the Party entity.
They share all the attributes of their parent but have specificities.

When inheritance is used:

When using inheritance, the underlying physical tables generated for the child entities and parent entity are the same. They contain a superset of all the attributes in the cluster of entities.

Display Options

Entities also have display options, including:

These display characteristics are detailed in the Working with Model Display chapter.

Integration Rules

In addition to the display characteristics, an entity is designed with integration rules describing how master data is created and certified from the source data published by the source applications.
These characteristics are detailed in the Integration Process Design chapter.

Creating an Entity

Creating a New Entity

To create an entity:

  1. Right-click the Entities node and select Add Entity.... The Create New Entity wizard opens.
  2. In the Create New Entity wizard, check the Auto Fill option and then enter the following values:
  3. Click the Next button.
  4. In the Primary Key Attribute screen, check the Auto Fill option and then enter the following values:
    1. Click Finish to close the wizard. The Entity editor opens.
  5. In the Description field, optionally enter a description for this entity.
  6. Press CTRL+S to save the editor.

When an entity is created, it contains no attributes. Simple Attributes and Complex Attributes can be added to the entity now.

Note: You cannot modify the entity matching behavior, primary key or inheritance from the Entity editor. To change such key properties of the entity after creating it, you must use the Alter Entity option. See Altering an Entity for more information.

Adding a Simple Attribute

To add a simple attribute:

  1. Expand the entity node, right-click the Attributes node and select Add Simple Attribute.... The Create New Simple Attribute wizard opens.
  2. In the Create New Simple Attribute wizard, check the Auto Fill option and then enter the following values:
  3. Click Finish to close the wizard. The Simple Attribute editor opens.
  4. In the Description field, optionally enter a description for the simple attribute.
  5. Press CTRL+S to save the editor.

Adding a Complex Attribute

To add a complex attribute:

  1. Expand the entity node, right-click the Attributes node and select Add Complex Attribute.... The Create New Complex Attribute wizard opens.
  2. In the Create New Complex Attribute wizard, check the Auto Fill option and then enter the following values:
  3. Click Finish to close the wizard. The Complex Attribute editor opens.
  4. In the Description field, optionally enter a description for the complex attribute.
  5. Press CTRL+S to save the editor.

Working with Attributes

It is possible to edit, order or delete attributes in an entity from the Attributes list in the entity editor.

To order the attributes in an entity:

  1. Open the editor for the entity.
  2. Select the Attributes item in the sidebar.
  3. Select an attribute in the Attributes list and use the Move Up and Move Down buttons to order this attribute in the list.

Note: With entities inheriting attributes from a parent in the context of Inheritance and have additional (not inherited) attributes, you can perform this ordering from the Inherited Attributes (All) section. Note that it is not possible to order additional attributes before the inherited attributes.

To delete attributes from an entity:

  1. Open the editor for the entity.
  2. Select the Attributes item in the sidebar.
  3. Use the Delete buttons to remove the attribute from the list.
  4. Click OK in the confirmation dialog.

Note: With entities inheriting attributes from a parent in the context of Inheritance and have additional (not inherited) attributes, you can delete attributes from the Inherited Attributes (All) section.

Important: Deleting an inherited attribute on a child entity removes it from the parent entity, and by extension from all the child entities inheriting this attribute from the parent.

Altering an Entity

Altering an entity allows modifying the key properties of an entity, including its matching behavior, inheritance and primary key attribute.

To alter an entity:

  1. Select the entity node, right-click and select Alter Entity. The Modify Entity wizard opens.
  2. In the wizard, modify the properties of the entity using the same process used for creating an entity

Reference Relationships

Reference Relationships functionally relate two existing entities. One of them is the referenced, and one is referencing.
For example:

They are used for:

A reference is expressed in the model in the form of a foreign attribute that is added to the referencing attribute.

To create a reference relationship:

  1. Right-click the Reference Relationships node in the model and select Add Reference.... The Create New Reference Relationship wizard opens.
  2. In the Create New Reference Relationship wizard, check the Auto Fill option and then enter the following values:
  3. In the Referencing [0..*] group, enter the following values:
  4. In the Referenced [0..1] group, enter the following values:
  5. Click Finish to close the wizard. The Reference Relationship editor opens.
  6. In the Description field, optionally enter a description for the Reference Relationship.
  7. Press CTRL+S to save the editor.
  8. Close the editor.

Data Quality Constraints

Data Quality Constraints include all the rules in the model that enforce a certain level of quality on the entities. These rules include:

The Mandatory Attributes and LOV Validations are designed when creating the Entities. The references are defined when creating Reference Relationships.
In this section, the Unique Keys and Validations are described. Refer to the previous sections of the chapter for the other constraints.

More information:

Unique Keys

A Unique Key defines a group of attributes should be unique for an entity.

  1. Expand the entity node, right-click the Unique Keys node and select Add Unique Key.... The Create New Unique Key wizard opens.
  2. In the Create New Unique Key wizard, check the Auto Fill option and then enter the following values:
  3. Click Next.
  4. In the Key Attributes page, select the Available Attributes that you want to add and click the Add >> button to add them to the Key Attributes.
  5. Use the Move Up and Move Down buttons to order the selected attributes.
  6. Click Finish to close the wizard. The Unique Key editor opens.
  7. In the Description field, optionally enter a description for the Unique Key.
  8. Press CTRL+S to save the editor.
  9. Close the editor.

Note: In the data certification processes unique keys are checked after the match and consolidation process, on the consolidated (merged) records. Possible unique key violations are not checked on the incoming (source records).

Note: Unique keys can be checked in data entry workflows to verify whether records with the same key have been entered previously by a user. This option is available only for entities using ID Matching. Besides, source records submitted to the hub via external loads (not via workflows) are not taken into account in such check. A unicity check enforced in a workflow will behave similarly to the check performed in the data certification process only if the consolidation rule gives precedence to the data submitted by users via workflows over data submitted by applications via external loads, of if data is only submitted via workflows.

Validations

A record-level validation validates the values of a given entity record against a rule. Several validations may exist on a single entity.

There are two types of validation:

SemQL Validation

To create a SemQL validation:

  1. Expand the entity node, right-click the Validations node and select Add SemQL Validation.... The Create New SemQL Validation wizard opens.
  2. In the Create New SemQL Validation wizard, check the Auto Fill option and then enter the following values:
  3. Click Finish to close the wizard. The SemQL Validation editor opens.
  4. Press CTRL+S to save the editor.
  5. Close the editor.

Plug-in Validation

Note: Before using a plug-in validation, make sure the plug-in was added to the platform by the administrator. For more information, refer to the "Semarchy Convergence for MDM Administration Guide".

To create a plug-in validation:

  1. Expand the entity node, right-click the Validations node and select Add Plug-in Validation.... The Create New Plug-in Validation wizard opens.
  2. In the Create New Plug-in Validation wizard, check the Auto Fill option and then enter the following values:
  3. Click Finish to close the wizard. The Plug-in Validation editor opens. The Plug-in Params and Plug-in Inputs tables show the parameters and inputs for this plug-in.
  4. You can optionally add parameters to the Plug-in Params list:
    1. In the Plug-in Params table, click the Define Plug-in Parameters button.
    2. In the Parameters dialog, select the Available Parameters that you want to add and click the Add >> button to add them to the Used Parameters.
    3. Click Finish to close the dialog.
  5. Set the values for the parameters:
    1. Click the Value column in the Plug-in Params table in front a parameter. The cell becomes editable.
    2. Enter the value of the parameter in the cell, and then press Enter .
    3. Repeat the previous steps to set the value for the parameters.
  6. You can optionally add inputs to the Plug-in Inputs list:
    1. In the Plug-in Inputs table, click the Define Plug-in Inputs button.
    2. In the Input Bindings dialog, select the Available Inputs that you want to add and click the Add >> button to add them to the Used Inputs.
    3. Click Finish to close the dialog.
  7. Set the values for the inputs:
    1. Double-Click the Expression column in the Plug-in Inputs table in front an input. The SemQL editor opens.
    2. Edit the SemQL expression using the attributes to feed the plug-in input and then click OK to close the SemQL Editor.
    3. Repeat the previous steps to set an expression for the inputs.
  8. Press CTRL+S to save the editor.
  9. Close the editor.

Diagrams

A Diagram is a graphical representation of a portion of the model or the entire model.
Using the Diagram, not only you can make a model more readable, but you can also create entities and references in a graphical manner, and organize them as graphical shapes.

It is important to understand that a diagram only displays shapes which are graphical representations of the entities and references. These shapes are not the real entities and reference, but graphical artifacts in the diagram:

Creating Diagrams

To create a diagram:

  1. Right-click the Diagrams node and select Add Diagram.... The Create New Diagram wizard opens.
  2. In the Create New Diagram wizard, check the Auto Fill option and then enter the following values:
  3. Click Finish to close the wizard. The Diagram editor opens.

Working with Entities and References

In this section, the creation/deletion of entities and references from the diagram is explained.

To create an entity using the diagram:

  1. In the Palette, select Add Entity.
  2. Click the diagram. The Create New Entity wizard opens.

Follow the entity creation process described in the Creating an Entity section.

The entity is created and a shape corresponding to this entity is added to the diagram.
Note that you can also create, edit and delete attributes from the diagram. Select an attribute or entity and use the context menu options.

To create a reference using the diagram:

  1. In the Palette, select Add Reference.
  2. Select the referencing entity in the diagram. Keep the mouse button pressed, and move the cursor to the referenced entity.
  3. Release the mouse button. The Create New Reference wizard opens. It is pre-filled based on the two entities.

Follow the reference relationship process described in the Reference Relationships section.

The reference is created and a shape corresponding to this reference is added to the diagram.

To delete a reference or an entity from the diagram:

  1. In the diagram, select the entity of reference that you want to delete.
  2. Right-click and select Delete.
  3. Click OK in the Confirm Delete dialog.

The reference or entity, as well as the shape in the diagram disappear.

Important: Deleting an entity or reference cannot be undone.

Working with Shapes

In this section, the creation/deletion of shapes in the diagram without changing the real entity or reference is explained.

To add existing entities to the diagram:

  1. In the Palette, select Add Existing Entity.
  2. Click the diagram. The Selection Needed dialog opens showing the list of entities in the diagram.
  3. Select the entities to add to the diagram.
  4. Click OK. The shapes for the selected entities are added to the diagram.

You can repeat this operation if you want to add multiple shapes for an entity in the diagram.

To add existing references to the diagram:
It is not possible to manually create a shape for reference in a diagram.
When an entity is added to the diagram, shapes for the references relating this entity to entities already in the diagram are automatically added.

To remove a shape from the diagram:

  1. In the diagram, select the shape representing the entity of reference that you want to delete.
  2. Right-click and select Remove Shape.

The shape disappears from the diagram. The entity or reference is not deleted.

Database Reverse-Engineering

Reverse-engineering can be used to quickly populate a model from table structures stored in a schema.
During this process, entities are created with attributes named after the column names.

Note: This process connects to a database schema using a JDBC datasource that must be previously configured on the application server for the Semarchy Convergence for MDM application. Please contact the application server administrator for declaring this datasource.

Note: Reverse-engineering is provided as a one-shot method to quickly populate the initial model from a database schema. The entities created using a reverse-engineering are by default fuzzy matching entities. Foreign keys existing between the tables in the schema are not reverse-engineered as references in the model. Besides, the reverse-engineering process is not incremental.

To perform a database reverse-engineering:

  1. Select the Entities node in the model.
  2. Right-click and select Database Reverse-Engineering. The Reverse-Engineer Tables to Entities appears.
  3. Select the Datasource to Reverse-Engineer from the list.
  4. Click Next . The list of tables and columns is reverse-engineered. At issue, an Entity Preview page shows the list of tables and columns and the suggested logical names for these.
  5. Select only those of the entities and attributes that you want to reverse-engineer.
  6. Modify the logical and physical names in this page.
  7. Press Finish . The entities and attributes are created according to your definition.

Note: The entities created via a reverse-engineering process are provided as is. It is recommended to review their definition, particularly the Matching Behavior .

Model Variables

Model variables store values retrieved from remote servers (declared as Variable Value Providers). Variable values are local to each user session, and are refreshed when the user accesses Semarchy Convergence for MDM. Model variables can be used in SemQL filters and expressions created at design and run-time to adapt the experience to the connected user.

For more information about Variable Value Providers, see the "Configuring Variable Value Providers" section in the "Semarchy Convergence for MDM Administration Guide".

Creating Model Variables

Note: Before creating model variables, make sure that the variable value providers from which you want to retrieve information are declared for your Convergence for MDM instance.

To create a model variable:

  1. Right-click the Model Variables node and select Add Model Variable.... The Create New Model Variable wizard opens.
  2. In the Create New Model Variable wizard, check the Auto Fill option and then enter the following values:
  3. Click Next.
  4. Select the Edit Expression button.
  5. In the Variable Lookup Query dialog, enter the query to retrieve the variable value:
  6. Click Finish to close the wizard. The Model Variable editor opens.
  7. Press CTRL+S to save the editor.
  8. Close the editor.

Variable Lookup Queries

The variable lookup query defined in a model variable retrieves information from a variable value provider. This information can be made specific to the connected user using the V_USERNAME variable.

The built-in variable called V_USERNAME stores the connected user name, and can be referred to in the variable lookup queries using the following syntax:

Warning: Lookup queries should return a single value (column) and a single result (record). If the query returns multiple results or multiple values, only the first value of the first result is taken into account and set in the variable value.

Note: It is not possible to use a variable in the lookup query of another variable.

Testing Model Variables

After creating a new model variable, it is recommended to test it.

To test a model variable:

  1. In the Model Edition view, double-click the model variable. The Model Variable editor for this variable opens.
  2. In the editor toolbar, click the Retrieve Current Value button.
  3. The variable value refreshed for the current session appears in the Current Value field of the editor. If the variable cannot be refreshed, an error is issued.

Using Model Variables

Model Variable can be used in the following SemQL expressions:

In these SemQL expressions, you can bind the model variable using the :<variable name> syntax. You can also use in these expressions the built-in :V_USERNAME bind variable.

For example, to create a privilege grant allowing the connected user to see only his own record in the Employee master data:

The connected user will be granted these privileges only for the master data record matching this expression.

Note: Variable values are not persisted. They are retrieved when the user connects, and disposed at the end of the user session. If the content of the Variable Value Provider (Remote LDAP Directory or Database) is modified, the changes are taken into account only when the user re-connects to Semarchy Convergence for MDM.

Display Names

Certain display properties are defined as part of the logical modeling effort.
The Labels and Descriptions provided when creating and editing the entities, attributes, types and references are are used when displaying the entities of the model in the context of applications, and as default labels and descriptions when using attributes from these entities. Other artifacts specific to displaying a model can be defined in the model. They include the Entity Display Names and Complex Types Display Names, described in the following sections.

Entity Display Names

An entity is a structure containing several attributes (simple and complex). When an entity value needs to be displayed in a compact form (for example, in a table, or in a single field), the Display Name is used.

The display name defines how an entity is displayed in compact form. It is a concatenation of several attributes, separated by a Separator.
For example, a Contact entity is shown as <first name>˽<last name>.

To create or modify an entity display name:

  1. Right-click the entity node and select Define Display Name.... The Modify Display Name wizard opens.
  2. In the Modify Display Name wizard, enter the following values:
  3. Click Next.
  4. In the Display Name Attributes page, select the Available Attributes that you want to add and click the Add >> button to add them to the Selected Attributes.
  5. Use the Move Up and Move Down buttons to order the selected attributes.
  6. Click Finish to close the wizard.
  7. Press CTRL+S to save the Display Name editor.
  8. Close the editor.

Note: Only one display name can be created for a given entity.

Note: The default display name of the entity can be customized when the entity is used:
* In a business object view transition referring to this entity, you can customize the string displayed for this entity in the hierarchy.
* In a form view that refers to this entity, you can customize the string displayed for the entity in the form.
Both these customizations are expressed as SemQL expressions that use the attributes of the entity.

Complex Type Display Name

A complex type is a structure containing several attributes. When a complex attribute value needs to be displayed in a compact form (for example, in a table, or in a single field), the Display Name is used.

The display name defines how a complex attribute is displayed in compact form. It is a concatenation of several definition attributes, separated by a Separator.
For example, the GeocodedAddress complex type contains a large number of attributes, from the simple StreetNumber down to the longitude and latitude. A display name would be for example: StreetNumber StreetName City Country .

To create or modify a complex attribute display name:

  1. Right-click the complex attribute node and select Define Display Name.... The Modify Display Name wizard opens.
  2. In the Modify Display Name wizard, enter the following values:
  3. Click Next.
  4. In the Display Name Attributes page, select the Available Attributes that you want to add and click the Add >> button to add them to the Selected Attributes.
  5. Use the Move Up and Move Down buttons to order the selected attributes.
  6. Click Finish to close the wizard.
  7. Press CTRL+S to save the Display Name editor.
  8. Close the editor.

Note: Only one display name can be created for a given complex type.