Reltio Connect

Hi Klaudia -  I don't think it is possible, but I am tagging our RDM product manager @Abhilasha Sabharwal to double confirm

Any news?
Otherwise we have to delete all our localization data and that would be a pity.

Hi Klaudia -  I don't think it is possible, but I am tagging our RDM product manager @Abhilasha Sabharwal to double confirm

Hi Klaudia,

Thank you for your patience, and apologies for the delay.
You've read the behavior correctly, and I want to set expectations clearly: this is how Reltio works today by design. When an RDM lookup value is shown in the UI, we display the localization that matches the user's browser locale, and fall back to the canonical value only when no matching localization exists. There's currently no setting that forces the canonical value to display when a localization is present - for a given locale, the localized value always takes precedence.

To make sure I point you in the right direction, it would help me to understand your use case a little better:
1. Could you share a bit more on the goal behind defining the localizations, given that you'd like the canonical abbreviation (g/ha) to be what users see?
2. Where exactly do you need the abbreviation shown (e.g., Hub UI profile, search, exports), and for which users or locales?

Best regards, 
Abhilasha Sabharwal 
Product Manager, RDM - Reltio

Any news?
Otherwise we have to delete all our localization data and that would be a pity.

Hi Klaudia -  I don't think it is possible, but I am tagging our RDM product manager @Abhilasha Sabharwal to double confirm

Thanks Abhilasha for your detailed answer.

Here my answers:

1. Units are typically abbreviated. We loaded the long texts in different languages to the RDM localization to have a definition for unknown or special units.
2. The abbreviation should be shown in MDM where the user selects a unit. In science it is better to show a unit as abbreviation.

OK. Then we will delete our localization data and put only the English localization value to a custom attribute in the RDM lookup type.

Hi Klaudia,

Thank you for your patience, and apologies for the delay.
You've read the behavior correctly, and I want to set expectations clearly: this is how Reltio works today by design. When an RDM lookup value is shown in the UI, we display the localization that matches the user's browser locale, and fall back to the canonical value only when no matching localization exists. There's currently no setting that forces the canonical value to display when a localization is present - for a given locale, the localized value always takes precedence.

To make sure I point you in the right direction, it would help me to understand your use case a little better:
1. Could you share a bit more on the goal behind defining the localizations, given that you'd like the canonical abbreviation (g/ha) to be what users see?
2. Where exactly do you need the abbreviation shown (e.g., Hub UI profile, search, exports), and for which users or locales?

Best regards, 
Abhilasha Sabharwal 
Product Manager, RDM - Reltio

Any news?
Otherwise we have to delete all our localization data and that would be a pity.

Hi Klaudia -  I don't think it is possible, but I am tagging our RDM product manager @Abhilasha Sabharwal to double confirm

Hi Klaudia,

Thank you - that's really helpful context, and it makes complete sense that in a scientific setting you'd want the abbreviation shown while keeping the full definitions available for reference.

Before you delete the localization data, I'd like to make sure we're not removing something that may be referenced elsewhere. Could you share a little about how you currently maintain these lookups - for example, how they're loaded/updated (UI, API, file), and whether the localization values are consumed anywhere downstream (exports, reporting, integrations, or other applications)? That will help us avoid any unintended impact.

I'd also like to suggest an alternative modeling approach that may give you what you want without losing your data. In an RDM lookup type, each member has both a canonical code and a canonical value. Rather than putting the abbreviation in the canonical value, you could:

1. Use the canonical code to store the abbreviation (e.g., g/ha), and
2. Use the canonical value for the full descriptive name (e.g., "Gram per Hectare").
In MDM, the dropdown can display values in the canonical value (canonical code) format - so the user would see Gram per Hectare (g/ha), giving them both the full definition and the abbreviation together at the point of selection. This keeps the abbreviation visible while preserving your full descriptive text, so you can retain your existing localizations rather than deleting them.

Would this approach fit how you use units in MDM? 

Best regards,
Abhilasha Sabharwal
Product Manager, RDM - Reltio

Thanks Abhilasha for your detailed answer.

Here my answers:

1. Units are typically abbreviated. We loaded the long texts in different languages to the RDM localization to have a definition for unknown or special units.
2. The abbreviation should be shown in MDM where the user selects a unit. In science it is better to show a unit as abbreviation.

OK. Then we will delete our localization data and put only the English localization value to a custom attribute in the RDM lookup type.

Hi Klaudia,

Thank you for your patience, and apologies for the delay.
You've read the behavior correctly, and I want to set expectations clearly: this is how Reltio works today by design. When an RDM lookup value is shown in the UI, we display the localization that matches the user's browser locale, and fall back to the canonical value only when no matching localization exists. There's currently no setting that forces the canonical value to display when a localization is present - for a given locale, the localized value always takes precedence.

To make sure I point you in the right direction, it would help me to understand your use case a little better:
1. Could you share a bit more on the goal behind defining the localizations, given that you'd like the canonical abbreviation (g/ha) to be what users see?
2. Where exactly do you need the abbreviation shown (e.g., Hub UI profile, search, exports), and for which users or locales?

Best regards, 
Abhilasha Sabharwal 
Product Manager, RDM - Reltio

Any news?
Otherwise we have to delete all our localization data and that would be a pity.

Hi Klaudia -  I don't think it is possible, but I am tagging our RDM product manager @Abhilasha Sabharwal to double confirm