Unify and manage your data

Profiles at a glance

Learn about Profiles in the Hub.

Reltio Multidomain MDM Reltio Customer 360

Reltio platform provides the ability to manage a variety of data entities using Hub. A profile is a collection of all the data associated with an entity.

Profiles contain the attributes for an entity, relationships for an entity, and sources for all of the attributes. It is possible that an entity attribute can have multiple sources and multiple values. The Operational Value (OV) is the current value for a given attribute, as defined by the survivorship rule for the attribute. The Profile pages enable you to view and manage the details for each entity in your tenant.

Is an entity and a profile the same?

A Reltio profile and a Reltio entity are subtly different, even though we tend to use the words interchangeably. An entity is a record; it has attributes (simple, nested and reference) and is treated as a node in the Reltio graph. A profile is a broader concept and refers to not only the entity of interest but all of the entities (nodes) connected directly to the entity via relationships, and all of the entity’s interaction data. So then a profile is really the 360 degree expression of an entity.

For more information about profiles, see topic Profile management at a glance.

Display attributes in all modes

When you use the viewing, editing, or suggesting modes, attributes without values are not displayed by default in the Profile view. However, if you want to view such attributes in all modes, include the alwaysVisible option in your UI configuration file. Add a list of attributes under a specific entity type, that you want to be visible in all these modes, as shown below:

"configuration/entityTypes/HCP": {
  ...,
  "views": [
    {
      "component": "Attributes",
      ...,
      "alwaysVisible": [
        "configuration/entityTypes/HCP/attributes/CallingName"
      ]
    }
  ]
}

In the above example, we have included the CallingName attribute as part of the alwaysVisible option. This ensures that the attribute is visible in all modes, even if a value is not defined for it. To update the UI configuration, see topic Export and Import of UI Configuration Files.