External Entities

1 Introduction

External entities can be added to the Domain Model through the Data Hub pane. They are displayed as purple entity containers in the Domain Model. External entities represent the link to the datasets that are made available through the shared data sources registered in Mendix Data Hub. Data sources are collections of entity sets (that are referred to as datasets) are published in OData services.

Datasets are maintained and updated in the source application. You can integrate or consume these datasets through external entities in your app development, and any changes to the data in the originating app is automatically updated in the consuming apps.

External entities can be used with local entities. However, as the datasets are maintained in the source applications, not all properties can be changed in the consuming app.

To follow how to add external entities from the Data Hub pane, see Adding External Entities.

2 Adding an External Entity to an App

To add an external entity to your app model, follow these steps:

1. In the Domain Model of you app model search in the Data Hub pane for the entity or data source that you want to use in your app.

   In the Catalog, an OData service may be registered multiple times with different version numbers or deployed to different environments, all exposing the entity (dataset) that you may want to use. Search the Catalog first and find the one most relevant to the requirements for your app.

2. Drag the entity into the Domain Model.

3. The entity and its attributes are then added to your app and two documents are added in the App Explorer:

   • the Consumed OData Service document that contains details of the OData service and the metadata; the logo displayed identifies the originating app of the service

   • the OData Location that specifies the location constants for the service

     

For further information, see Consumed OData Service.

The consumed entities of the current app are listed in the Used in your App section of the Data Hub pane:

You can make local changes to the properties of external entities that only affect how the data is used and presented in the consuming app. All other properties are defined in the source application and cannot be changed. When multiple external entities from the same OData service are used in a module or app, associations between the entities (made in the source app) will automatically be made in the local module.

For more information on using published OData services and entities through the Catalog, see How to Consume Registered Assets in the Data Hub Guide.

2 Properties of External Entities

Compared to local entities, external entities have a limited number of properties that can be changed. The rest of the properties are defined in the originating app and are, therefore, read-only.

2.1 General

This tab displays the general properties of the external entity. The values that are defined in the originating app are displayed but but cannot be edited. The values that can be edited will only apply to the local app:

• Name – the name of the entity in the local app
• Original name – this is read-only and shows the name of the entity as defined in the consumed OData service
• Summary – this is a read-only field and displays the description for the entity in the originating app

2.2 Attributes

The attributes that have been exposed in the OData service for the external entity are listed here. All changes that are made to the attributes and the attribute list are applied to the local instance of the entity. As they are consumed, these changes will not affect the metadata of the consumed service that the entity is exposed in or the attributes of the entity in the originating app.

The following operations can be done on the displayed attribute list:

• Add – add attributes that were exposed in the OData service for the entity and were previously removed for this local instance
• Edit – edit the selected attribute from the Edit Attribute form
• Remove – remove an attribute from list

2.2.1 Edit Attribute

The Edit Attribute box can be used for specifying a local name for the attribute and adding a local description.

• General Tab
  • Name – a local name for the attribute can be specified.
  • Original Name – this is a read-only value that displays the original name of the attribute as given in the originating app
  • Summary – a read-only summary displaying the description for the attribute in the originating app; to enter a local description, add this in the Documentation tab
  • Type – read-only vlues for the Type and Length and Max. Length of the attribute as defined in the originating app
• Documentation – a description for the attribute that is displayed for users of the current app

2.3 Associations

This tab displays the associations that the external entity has with other entities that are exposed in the same service and also any associations that have been made with local entities. For further details on association properties in Studio Pro see Association Tab Properties.

If the entity contains one-way navigable associations, there is a note at the top of the dialog box.

The following apply for all associations with the external entity:

Navigability icon – an icon indicating whether an association is one-way navigable Name – name of the association as displayed in the current app Type – read-only for associations between two external entities Owner – read-only for associations between two external entities Parent – read-only for associations between two external entities Child – read-only for associations between two external entities

You can Add and Edit associations to the external entity with a local entity. However, the association cannot be made from an external entity to a local entity: the local entity must be the owner of the association.

If you use an external entity in your app and this entity is associated with other external entities from the same OData service in your app, the association will automatically be added in the domain model and be listed here.

2.3.1 Association Properties

When you Edit an association that is included for two entities exposed in the same OData service, the following properties are displayed and the only local change that can be made is the local Name:

• Name – local name of the association
• Original Name – read-only name of the association given to it in the originating app
• Summary – read-only description of the association from the originating app
• Multiplicity – read-only multiplicity values from the originating app
• Documentation – go to this tab to add a local description for the external entity association

If the association is one-way navigable, there is a note at the top of the dialog box.

2.3.2 Connecting Two External Entities

If you want to connect two external entities that are not connected in the originating app, this is not possible as the relationship to the data cannot be influenced locally. However, you can add a local entity and connect this local entity with both external entities. The local entity must be the owner of both associations, in this case.

2.4 Documentation

You can add any local information about the external entity in this tab.

3 Authentication

Using external entities in production environments requires both publishers and consumers of OData services to set the correct authentication method.

3.1 Publishers: Setting Authentication Method

Publishers of an OData service set the type of authentication needed for it to be consumed. The following authentication methods are available:

• Username and password (basic authentication)
• Active session
• Custom (calling an authentication microflow)
  • Mendix SSO
  • Other (add your own, using a custom module for example)

For details on the types of authentication methods and how to set them up, see the Security section of Published OData Services.

3.2 Consuming External Entities with Authentication

When an external entity is used in an app module through the Data Hub pane, a consumed OData service document is added specifying the details of the consumed service. This is the API to the publishing app and the data associated with the entity.

If the service you are consuming requires authentication, you will need to add authentication credentials. Consumers of an OData service in an external entity can contact the owner of the data source to check the required authentication method and credentials.

Learn more about adding authentication information to a consumed OData service:

• Configuring username and password consuming apps
• Using HTTP headers for consuming custom authentication methods
• Consuming a service that uses [Mendix SSO][/refguide9/consumed-odata-service/#authenticate-mendix-sso]

4 External Entity Limitations

External entities are the endpoints that are defined in the published OData service from the originating app. The consumed OData service document displays the values from the service metadata when the external entity is used through the Data Hub pane. The datasets associated with the entities are maintained in the originating apps.

Furthermore, external entities cannot be committed. Use the Send External Object activity to persist changes to external entities. This means the following:

• The Commit activity does not work. Use Send External Object instead.
• On pages, the Save button and the Save Changes event do not work when the page contains widgets that update external entities. Call a microflow that persists the changes using Send External Object instead.

For more details on consuming services and exposed entities, including operations that can be performed on external entities, see Consume Registered Assets in the Data Hub Guide.