Reltio attribute types

Learn about the unique Reltio attributes for data types.

Reltio Cloud defines a small set of proprietary attribute types you can use to create the attributes in your entities, relationships, and interactions. Take advantage of this small, easy-to-understand set of attribute types and their powerful modeling capabilities in a simple and intuitive manner.

Understanding the Reltio attribute type

Learn what an attribute type is and what the different expressions of Reltio attributes are.

Reltio Multi-domain MDM makes defining your data model simple and intuitive. Our MDM provides a set of attribute types that help you:
  • Build a logical data model, rather than relying on physical tables and foreign keys.
  • Define entities, relationships, and interactions in granular detail.
  • Make detailed data available to content and interaction designers.
  • Provide business users with rich, yet streamlined, search and navigation experiences.
Reltio MDM provided attribute types:
  • Simple attribute type
  • Nested attribute type
  • Reference attribute type
  • Analytic attribute type

Simple attribute type

The simple attribute type represents a single characteristic of an entity, relationship, or interaction. It is the only manifestation of the attribute type in Reltio Multidomain MDM that you must define as a data type. The nested, reference and analytic attribute types represent combinations or collections of simple sub-attribute types.

Simple attribute definitions

Let’s look at this list of available data types for defining the simple attribute type.
Table 1. Simple Attribute Data Types
Data Type of Simple Attribute Description Supported Format Additional Information
String Can be any text. Software limits the length of the value by the maxAttributeValueSize parameter in the physical configuration, where the default length is 10240 characters.
Int, Integer, Long, Dollar

Reltio platform considers all these types as Long java type.

Values of these data types are indexed as 64-bit integer numbers in the search engine with the following values:

  • A minimum value of -2^63
  • A maximum value of +2^63
Float, Double, Number

Can be any value that can be parsed to the Double java object (Double.parseDouble(value).

The software indexes the values of these data types as 32-bit floating-point numbers in the search engine.

Note: If you want to store integer values in Float, Double, and Number data types, note the following important points:

  • A minimum integer value is -16777217
  • A maximum integer value is +16777217

Storage of values outside the range mentioned above results in loss of precision and unexpected search results.

Boolean Can be any value that can be parsed to the Boolean java object (Boolean.parseBoolean(value) . Possible values considered as true or false. Look at the possible values for Java type Boolean (java/lang/Boolean.java).
Date, Time, Timestamp Software uses Date to capture calendar date information in multiple formats.

Supported Date formats:

  • yyyy-MM-dd
  • MM/dd/YYYY
  • MM.dd.YYYY
  • MM-dd-YYYY
  • YYYY/MM/dd
  • YYYY-MM-dd
  • YYYY.MM.dd
  • YYYYMMdd
Supports the Time format but does not consider extra information, such as hours and minutes.
Time and Timestamp are the same types.

Supported formats for Time and Timestamp :

  • YYYY-MM-’d’T'HH:mm:ss.SSSZ
  • yyyy-MM-’d’T'HH:mm:ssZZ
  • yyyy-MM-’d’T'HH:mm:ss.SSSZZ
  • MM/dd/YYYY HH.mm
  • MM.dd.YYYY HH.mm
  • MM-dd-YYYY HH.mm
Supports the Date format but the missing information, such as hours and minutes are filled in by zeros.
Blob This type of attribute stores multiline text data. Can enter any text in a blob. But can’t use same text for searching because the value represents binary data.
URL, Blog URL, Image URL Can be any text and displays as a link on the Hub. Can wrap text, if needed.

Nested attribute type

You can use the nested attribute type to create collections of simple attributes by nesting them. The nested attribute can help you make your user interface (UI) more functional.

Let’s look at an example of a phone number—that’s a nested attribute. You break the phone number down by using nested sub-attributes. The typical sub-attributes of a phone number include:
  • Number
  • Type
  • Area code
  • Extension

Continuing with the phone number example, the sub-attributes are only meaningful when held together as a collection. When posted as a nested attribute, the entire collection represents a single instance, or value, of the nested attribute. Posts of additional collections are also valid and serve to accumulate additional nested attributes within the entity, relationship, or interaction data type.

Why use the nested attribute type?

Use the nested attribute type when you want to improve the appearance and usablity of your user interface (UI). The nested attribute can provide greater flexibility to your user interface designers and improve the navigation experience for business users. Nested attribute types can help you when you:
  • Make an attribute more customized by including a broader collection of sub-attributes. For example, adding a phone number sub-attribute to a user profile attribute.
  • Group a set of attributes together to gain from their combined effectiveness. For example, a person’s physical description is clearer with many attributes.
  • Display nested sub-attributes in the UI. The expand-collapse capability of the nested attribute type lets you display sub-attributes of a nested attribute separately in the UI. For example, you can define a simple attribute type to capture singular physical details, such as eye color, hair color, height, and weight. Together, these simple sub-attributes comprise a nested attribute type named physical description, and you can display each independently or together in the UI.

Reference attribute type

You can use the reference attribute type to enable a single entity to reference and make use of the attributes of another entity. The referencing increases reuse of attributes and saves you time. The entity now functions as if the attributes of both were defined natively in each entity. The reference attribute type can help ease the defining of relationships between entity types in your data model.

Why use the reference attribute type?

  • Reuse attributes between entities. You don’t always have to define the attributes of every entity; some can share the attributes by reference. You can make an entity use the attributes of another entity without natively defining the attributes of both. For example, the L1 layer in the Reltio Multidomain MDM information model defines a relationship that links an Organization and an Individual using the affiliatedwith relationship type. The affiliatedwith relationship type defines the Organization entity type to be a reference attribute of the Individual entity type.
  • Easier navigation between entities. In the example we just covered, the entity types are related using the affiliatedwith relationship type. The relationship type there specifies an attribute of previous employer for the Individual entity type. This reference makes previous employer display as a hyperlink on the individual’s profile facet. From there, the user can navigate easily to the individual’s previous employer.
  • Easily refined search. When attributes of a referenced entity and relationship type are available to be indexed as though they were native to the referencing entity, business users can more easily refine search queries. For example, in a search of a data set that contains 100 John Smith records, entering John Smith in the search box returns 100 John Smith records. Adding Acme to the search criteria returns only those records with John Smith that have a reference, and so have an attribute, that contains the word Acme.

What you need to know before using reference attribute types

  • Defining relationship types. You must establish a relationship type between two entity types before you can define a reference attribute. After you’ve defined the relationship type, you can assign one entity type to be a reference of the other. To learn more about defining relationship types, see Entity Relationships.
  • Immutable When you have several entities that must all reference the same attribute of another entity, you can mark all sub-attributes of that reference attribute as immutable for some sources. To learn more about avoiding the generation of multiple events, see Immutable Reference Attributes.
  • Non-OV and OV values. The reference attribute type can contain operational values (OV), both non-OV and OV. To learn more about OV values, see Understanding the Reltio Entity Type.

Analytic attribute type

You can use the analytic attribute type to receive and hold values delivered by an analytics solution, such as Reltio Insights. Use the analytic attribute type when you want to make a value from your analytics solution available to a business user or to other applications using the Reltio Rest API.

What you need to know before using analytic attribute types

  • Different management in merges. For example, during merge operations, the attribute is managed differently from other attribute types when records come together.
  • Data delivery to your analytics solution. For example, maybe your analytics implementation calculates a customer’s lifetime value, and you want that value to be available to the user while they’re looking at the customer’s profile. You can define an analytic attribute to hold this value and provide instructions to Reltio Insights to deliver the result of the calculation to this attribute. To learn more about merging in Reltio, see Merging in the Reltio Platform.