Custom Label

Map My Relationships gives provision to customize the label name in both Relationship and Connection control. User can customize the label at relationship level, group level and measure level.

Relationship Level

'Node Label' field will auto-populate the value based on which relationship user selects. This value is the default Relationship node label.

User can customize this label by setting the 'Use Custom Label' field to Yes, which shows the Custom Label field where one can add the label.

Group Level (Cluster Nodes)

Similarly, user can change the label of group / cluster nodes. After selecting a Group By field, a preview of the same is shown in the Node Label field. To add the custom label, first change the value of Use Custom Label from No to Yes. Custom Label field will appear in which user can input the value to be displayed as a label on the Group node.

Here, {value} is the value on which the grouping has been done.

Measure Level (title)

In a similar manner as above, Measure title can also be customized. When user selects the field value in the Measure field, its display name (default preview label) is shown in Node Label field. User can add the custom label as shown below.

Custom Record Node Label

It defines record node labels dynamically based on selected fields within the configuration.

Users can customize this label further by selecting the “Record Node Label” field, which displays the Custom Label field where they can define the desired label.

Earlier, the Record Node Label always displayed an entity’s primary attribute value as the node label on the relationship map.

Now, the Record Node Label feature provides flexibility to customize what appears as the node label on the relationship map. By default, it continues to show the primary name attribute. However, you can configure a different field in the Entity Configuration to display your preferred value, as illustrated in the screenshot below.

When a field is selected in the configuration, the node label will show the value from that field. If the chosen field has no value, the system automatically falls back to displaying the entity’s primary attribute.

Example: If an admin wants to display a Contact record based on its Email Address, they can select the Email field in the configuration.

• If the contact has an email → the node label will show the email address.

• If the contact does not have an email → the node label will default to the contact’s primary attribute.