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
------------------------------
Abhilasha Sabharwal
------------------------------
Original Message:
Sent: 06-09-2026 06:22
From: Klaudia Augustin
Subject: How to inactivate RDM localization?
Any news?
Otherwise we have to delete all our localization data and that would be a pity.
------------------------------
Klaudia Augustin
Bayer AG
Monheim
------------------------------
Original Message:
Sent: 05-29-2026 05:22
From: Snehil Kamal
Subject: How to inactivate RDM localization?
Hi Klaudia - I don't think it is possible, but I am tagging our RDM product manager @Abhilasha Sabharwal to double confirm
------------------------------
Thanks,
Snehil Kamal
Senior Staff Forward Deployed Engineer
Reltio
Bangalore
------------------------------